You are right, but Ancuta, which developed the attached patch, tells me that the actual issue was when ser tried to generate an ACK on >299 responses for calls to such URNs.<br><br>Anyway, if we talk so much about this, it's not such a big deal, so here it is attached and here: <a href="http://svn.berlios.de/viewcvs/openimscore?view=rev&rev=631">http://svn.berlios.de/viewcvs/openimscore?view=rev&rev=631</a><br>
<br>Cheers,<br>-Dragos<br><br><br><div class="gmail_quote">On Fri, Jul 24, 2009 at 2:17 PM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Dragos Vingarzan schrieb:<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
* Core - support for emergency URI,<br>
<br>
<br>
What is this exactly? Any reference to ietf/itu specs?<br>
<br>
I am not really sure myself as somebody else did the implementation. But all the specs should be listed here: <a href="http://www.openimscore.org/emergency" target="_blank">http://www.openimscore.org/emergency</a> . And even for us this is still partly a branch with work in progress. The thing was that ser was even crashing when it got some of these, so in any case, even if not used, it would be a good patch.<br>
<br>
I'll have to do a diff and find out what was exactly changes as there were to many things in the last 3-4 years. And we probably have some garbage through that. I'll send the patch after some cleanup.<br>
</blockquote>
<br>
<br></div>
IIRC openser/ser can not parse service URNs. Usually, if a UAC initiates an emergency call, it looks like:<br>
<br>
INVITE urn:service:sos SIP/2.0<br>
Route: <a href="mailto:sip%3Auri-of-the-psap@example.com" target="_blank">sip:uri-of-the-psap@example.com</a>;lr<br>
From: <a href="mailto:sip%3Auser@domain.com" target="_blank">sip:user@domain.com</a>;tag=123<br>
To: urn:service:sos<br>
...<br>
<br>
Thus, the proxy does not even have to route based on the service URN, but just on the pre-loaded route-set. Nevertheless, the proxy must not crash or generate errors if the RURI and From/To URI does contain a service URN. Actually From/To/RURI are allowed to contain any URIs (also http URIs) - thus sr should supports parsing of these.<br>
<br>
regards<br><font color="#888888">
klaus<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Best Regards,<br>Dragos Vingarzan<br>