<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
They've been trying to push through a Session-id spec in the SIP
Dispatch IETF working group for some time. This is a globally unique
identifier that is carried across B2BUA's unmolested. Seems to
always fade away, but if it were actually ever passed as an RFC, you
could go to your vendor and ask them to implement it with some level
of confidence they'd actually do it in a way that's compatible with
all the other vendors.<br>
<br>
The last attempt was
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-kaplan-sip-session-id-03">http://tools.ietf.org/html/draft-kaplan-sip-session-id-03</a>, expired
March 2011. Some talk lately in the IETF of reviving it or a slight
permutation, though nothing specific that I'm aware of.<br>
<br>
Howard Hart<br>
<br>
<br>
On 03/15/2012 01:20 PM, Keith Croxford wrote:
<blockquote
cite="mid:CAHwxYOCS-ezu0f4JxCogtzXQZgn6Ofa-u2OHDStRds1JCOi0kA@mail.gmail.com"
type="cite">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.
<div>
<br>
</div>
<div>This works OK other than in one scenario. </div>
<div><br>
</div>
<div>Imagine that 4801001234@domain1 makes a call. Within this set
time window 1234@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@domain2 and
4801001234@domain1. </div>
<div><br>
</div>
<div>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.) </div>
<div><br>
</div>
<div>Keith </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">On Thu, Mar 15, 2012 at 11:56 AM,
Michael Lunsford <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:Michael.Lunsford@cbeyond.net">Michael.Lunsford@cbeyond.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Unfortunately, I don't have my fingers on one any longer.
Have you requested vendor support?<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On Mar 15, 2012, at 2:35 PM, Rakesh Unni wrote:<br>
<br>
Any tips on the setup mate?<br>
<br>
Much appreciated,<br>
Rakesh<br>
<br>
Sent from my iPad<br>
<br>
On 15 Mar 2012, at 16:53, Michael Lunsford <<a
moz-do-not-send="true"
href="mailto:Michael.Lunsford@cbeyond.net">Michael.Lunsford@cbeyond.net</a>>
wrote:<br>
<br>
> Palladion has options other than Call-ID that will
allow correlation of call legs including SDP.<br>
><br>
><br>
> On Mar 15, 2012, at 12:42 PM, Rakesh Unni wrote:<br>
><br>
> 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.<br>
><br>
> Thanks<br>
> Rakesh<br>
><br>
> On 15 March 2012 16:19, Hiers, David <<a
moz-do-not-send="true"
href="mailto:David.Hiers@adp.com">David.Hiers@adp.com</a><mailto:<a
moz-do-not-send="true"
href="mailto:David.Hiers@adp.com">David.Hiers@adp.com</a>>>
wrote:<br>
> 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....).<br>
><br>
> 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).<br>
><br>
><br>
><br>
> David<br>
><br>
><br>
> From: <a moz-do-not-send="true"
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>>
[mailto:<a moz-do-not-send="true"
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>>]
On Behalf Of Rakesh Unni<br>
> Sent: Thursday, March 15, 2012 08:47<br>
><br>
> To: <a moz-do-not-send="true"
href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><mailto:<a
moz-do-not-send="true"
href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>><br>
> Subject: [VoiceOps] Broadworks: Preserve sip
call-ID<br>
><br>
><br>
><br>
> Hi guys,<br>
><br>
> 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.<br>
><br>
> Is it possible on Broadworks to transparent proxy
the callID from the access side to the terminating side
?<br>
><br>
> Thanks<br>
> Rakesh<br>
><br>
> ________________________________<br>
> 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.<br>
><br>
><br>
><br>
><br>
> --<br>
> Rakesh<br>
><br>
> <a moz-do-not-send="true"
href="tel:%2B44%202033931856" value="+442033931856">+44
2033931856</a><br>
> <a moz-do-not-send="true"
href="mailto:sip%3Aunni@getonsip.com">sip:unni@getonsip.com</a><mailto:<a
moz-do-not-send="true"
href="mailto:sip%253Aunni@getonsip.com">sip%3Aunni@getonsip.com</a>><br>
><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a moz-do-not-send="true"
href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/voiceops"
target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>