[VoiceOps] Broadworks: Preserve sip call-ID

[Alex Balashov]

INSIPID?  Nice!  Made my day, and it's only 03:30.   But that's  going to be hard to top.

--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Atlanta, GA 30030
Tel: +1-678-954-0671
Web: http://www.evaristesys.com/, http://www.alexbalashov.com

Hadriel Kaplan <HKaplan at acmepacket.com> wrote:

>There's good news on that front -
>We've finally got a new IETF Working Group created for just that purpose: the "INtermediary-safe SIP session ID" Working Group, a.k.a. INSIPID.
>
>It's first meeting is in just a few days: this Monday, March 26th, at the IETF meeting.
>
>The meeting's in France, but the IETF has free remote participation - you can listen to the audio broadcast and be in a jabber chat room for the working group meeting.  And if you want to say something at the microphone, you just type what you want said into the jabber room and someone will say it for you in the physical room.
>All of that you can do remotely for free, without having to register, be a member, or sign up for anything.
>
>The current agenda is here:
>http://www.ietf.org/proceedings/83/agenda/agenda-83-insipid.txt
>The meeting's only an hour long, at 9:10-10:10am Eastern Daylight Time US.
>
>To join the audio and jabber session, go to the following page, search for "insipid", and click the little speaker icon for an audio stream, and the jabber lightbulb icon for a jabber URL.
>http://tools.ietf.org/agenda/83/
>Note you do need a jabber client to use that, but you can get them for free on all platforms; go to http://www.ietf.org/jabber/ for info on that.
>
>I urge anyone who cares about the issue to please join the meeting.  The more feedback we get, positive or negative, the faster we'll get somewhere. (well, I suppose if you say the whole idea is useless, then we won't get anywhere real fast :)
>
>Also, there's a new Working Group mailing list you can join, where the real action happens, here:
>https://www.ietf.org/mailman/listinfo/insipid
>Again, it's open to anyone who wants to join it.
>
>-hadriel
>
>
>On Mar 17, 2012, at 9:23 PM, Howard Hart wrote:
>
>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.
>
>The last attempt was http://tools.ietf.org/html/draft-kaplan-sip-session-id-03, expired March 2011. Some talk lately in the IETF of reviving it or a slight permutation, though nothing specific that I'm aware of.
>
>Howard Hart
>
>
>On 03/15/2012 01:20 PM, Keith Croxford wrote:
>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
>
>
>_______________________________________________
>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/20120323/86d4fde4/attachment-0001.html>