[VoiceOps] Broadworks: Preserve sip call-ID

Keith Croxford keith.croxford1 at gmail.com
Thu Mar 15 16:20:18 EDT 2012


I'm matching by multiple headers (to, from, pai, others) and these are
nested within a specific block of time. It's basically a few modifications
from the default call merging algorithm. I can't show
my exact modifications, but that should lead you in the proper path.

This works OK other than in one scenario.

Imagine that 4801001234 at domain1 makes a call. Within this set time window
1234 at domain2  initiates a call as well.  Even though I am set to match on
the last 6 characters of the caller/callee, Palladion is merging the calls
from 1234 at domain2 and 4801001234 at domain1.

I'm still working with IPTEGO to get a few of these bugs worked out. If I
knew how to (((write code in LISP)) it would be much easier accomplish.)

Keith



On Thu, Mar 15, 2012 at 11:56 AM, Michael Lunsford <
Michael.Lunsford at cbeyond.net> wrote:

> Unfortunately, I don't have my fingers on one any longer.  Have you
> requested vendor support?
>
>
> On Mar 15, 2012, at 2:35 PM, Rakesh Unni wrote:
>
> Any tips on the setup mate?
>
> Much appreciated,
> Rakesh
>
> Sent from my iPad
>
> On 15 Mar 2012, at 16:53, Michael Lunsford <Michael.Lunsford at cbeyond.net>
> wrote:
>
> > Palladion has options other than Call-ID that will allow correlation of
> call legs including SDP.
> >
> >
> > On Mar 15, 2012, at 12:42 PM, Rakesh Unni wrote:
> >
> > 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
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20120315/c91c819c/attachment.html>


More information about the VoiceOps mailing list