[VoiceOps] Broadworks: Preserve sip call-ID

[Marc STORCK]

CallID is different from CallerID.

CallID identifies the Call. CallerID identifies the Caller. (very much simplified explanation).

Regards,

Marc

From: Mary Lou Carey <marylou at backuptelecom.com<mailto:marylou at backuptelecom.com>>
Date: Thu, 15 Mar 2012 12:34:45 -0500
To: 'Rakesh Unni' <rakeshunni at gmail.com<mailto:rakeshunni at gmail.com>>, "'Hiers, David'" <David.Hiers at adp.com<mailto:David.Hiers at adp.com>>
Cc: <VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>>
Subject: Re: [VoiceOps] Broadworks: Preserve sip call-ID

The caller ID, LRN, and called number are used to determine the CABS billing (minutes of use) in the PSTN world so that's why they don't want you to drop callerID. Many VOIP carriers were dropping callerID or spoofing it so they could push it down a local trunk group and claim they didn't have to pay anything for it (because local is free). The recent FCC ruling on ICC reform stated that all carriers (including VOIP) are responsible for paying for their intra and interLATA traffic and must pass the correct information along so the traffic is classified and billed correctly.


Mary Lou Carey
BackUP Telecom Consulting
CLEC Consultant
OFF: 615-791-9969

From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org] On Behalf Of Rakesh Unni
Sent: Thursday, March 15, 2012 11:43 AM
To: Hiers, David
Cc: VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
Subject: Re: [VoiceOps] Broadworks: Preserve sip call-ID

It's Palladion  we are trying. Not sure why they worry about call-ID manipulation, guess it has some reference to the licensing   validation for transactions.

Thanks
Rakesh
On 15 March 2012 16:19, Hiers, David <David.Hiers at adp.com<mailto:David.Hiers at adp.com>> wrote:
Never had to try, but I've never seen anything in BW that is even close to this.  I know that you can't get them to take the "BW" out of the call-ID (sigh....).

You're asking for something that is pretty brittle. If you ever fork, you can't preserve the inbound call-ID on the multiple outbound legs, because call-IDs must be globally unique (RFC3261:8.1.1.4).



David


From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>] On Behalf Of Rakesh Unni
Sent: Thursday, March 15, 2012 08:47

To: VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
Subject: [VoiceOps] Broadworks: Preserve sip call-ID


Hi guys,

We are running r17 at the moment and currently testing a monitoring platform for both signalling and media. They use sip callID to identify call legs to merge and i would like to have all call legs on one call (from the originating access side to where we send the traffic to for PSTN). Since Broadworks act as a B2BUA it rewrites the originating callID to BW-xxxxx. I've made changes on the SBC to preserve the callID but now need Broadworks to preserve it.

Is it possible on Broadworks to transparent proxy the callID from the access side to the terminating side ?

Thanks
Rakesh

________________________________
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.



--
Rakesh

+44 2033931856
sip:unni at getonsip.com<mailto:sip%3Aunni at getonsip.com>


_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops