On a really bad day, you can make it work with a B2BUA in the middle. But really, the technology shouldn't act so dumb, right? :)<div><br></div><div><div class="gmail_quote">On Fri, Jul 10, 2009 at 2:13 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Brett is very right. I think one of the reasons I reacted instinctively to this scenario was because I tried to implement something similar with a well-known switch once (I think it was a Metaswitch) and the signaling agent reacted to my "spiral" (which I didn't know to be such) as though it were a "loop."<br>
<br>
Brett Nemeroff wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Just throwing this out.. Not all equipment can handle SIP Spiral properly. <cough> asterisk <cough> (although I know there was work done on Asterisk+SIP Sprial, I don't know where that ended up)<br>
<br>
so be careful before you spend a lot of time on that. I'd love to hear how all of that works for you. I've got plans to do something similar in the LNP space..<br>
-Brett<br>
<br></div><div class="im">
On Fri, Jul 10, 2009 at 2:02 PM, Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a> <mailto:<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>>> wrote:<br>
<br>
El Viernes, 10 de Julio de 2009, Alex Balashov escribió:<br>
> > npdi and rp are *userinfo* parameters (in fact they are TEL URI<br>
> > paremeters so when converting to SIP URI they become part of<br>
the userinfo<br>
> > part). <a href="http://www.tech-invite.com/Ti-sip-abnf.html#teluri" target="_blank">http://www.tech-invite.com/Ti-sip-abnf.html#teluri</a><br>
> ><br>
> > So, if the original RURI is:<br>
> > <a href="mailto:sip%3A%2B12345678@mydomain.org" target="_blank">sip:+12345678@mydomain.org</a><br></div>
<mailto:<a href="mailto:sip%253A%252B12345678@mydomain.org" target="_blank">sip%3A%2B12345678@mydomain.org</a>><div class="im"><br>
> ><br>
> > and OpenSIPS modifies it to:<br>
> > sip:+12345678;npdi=123;rn=<a href="mailto:456@mydomain.org" target="_blank">456@mydomain.org</a><br></div>
<mailto:<a href="mailto:456@mydomain.org" target="_blank">456@mydomain.org</a>><div class="im"><br>
> ><br>
> > then both RURI's are differents and the softsiwtch won't<br>
consider it a<br>
> > loop.<br>
> ><br>
> > However, if the parameters are added as SIP URI parameters<br>
(after the<br>
> > hostpart) the it would be a loop (except if they are maddr,<br>
user, ttl).<br>
><br>
> How does that change the other logical attributes of a call leg, i.e.<br>
> Call ID GUID, From tag, CSeq, etc?<br>
<br>
If the RURI changes, then it's *not* a loop, but a spiral. Re-read the<br>
appropiate section in RFC 3261 :)<br>
<br>
<br>
--<br></div>
Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a> <mailto:<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>>><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><div class="im"><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
<br></div>
------------------------------------------------------------------------<div class="im"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></blockquote>
<br><div><div></div><div class="h5">
<br>
-- <br>
Alex Balashov<br>
Evariste Systems<br>
Web : <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a><br>
Tel : (+1) (678) 954-0670<br>
Direct : (+1) (678) 954-0671<br>
</div></div></blockquote></div><br></div>