Hello guys,

 

Thanks for your quick answer.

 

Based on your confirmation that this format of the R-URI is supported and received inside the script (and not parsed by the sip stack), then I added additional logs and discovered the mistake in my script. I had before a line “subst_uri("/sip:([^:]*)[:;].*/sip:\1/");” in order to prevent unexpected R-URI format.

So when the line is removed, the $ru is complete as received. For me, it is not necessary to escape the URI.

 

So Kamailio supports implicitely Netann (RFC4240) R-URI format.

 

Best regards.

 

PatriceB

 

 

Hello,

for curiosity I did a test with r-uri (from the first email):

sip:annc@cl1.oms.ser.v0.pftest.net;play=http://1xx.1xx.1xx.1xx:8080/errfile/err.wav;repeat=forever

and one with r-uri (as suggested by Andreas):

sip:annc@cl1.oms.ser.v0.pftest.net;play=http%3A%2F%2F1xx.1xx.1xx.1xx%3A8080%2Ferrfile%2Ferr.wav;repeat=forever

In both cases the whole value was printed by $ru (in an xlog(...) function).

Can you add in config a line like:

    xlog("r-uri is [$ru]\n");

and what the output? Eventually, you can set debug=3 inc config and send all log messages for processing a request with such uri.

Cheers,
Daniel

Hi Patrice,

There are couple of characters in the URI which need to be escaped

properly. A correct R-URI would look like this:

sip:annc@cl1.oms.ser.v0.pftest.net;play=http%3A%2F%2F1xx.1xx.1xx.1xx%3A8080%2Ferrfile%2Ferr.wav;repeat=forever

There are string transformations "{s.escape.param}" and

"{s.unescape.param}" you can use (in case you get the full URI into your

config script, not sure whether the parser bails out first).

Andreas

On 06/04/2012 06:35 PM, patrice.bodeven@orange.com wrote:

Hello,

I’am working on Kamailio version 3.2.2.

I’m doing some test in interaction with Application server and media

server.

The applicationServer sends a INVITE sip to Media Server via the Kamailio.

The R-URI has the format

sip:annc@cl1.oms.ser.v0.pftest.net;play=http://1xx.1xx.1xx.1xx:8080/errfile/err.wav;repeat=forever

But the parsing done by Kamailio of $ru is trunked to

sip:annc@cl1.oms.ser.v0.pftest.net;play=http

1)      Could you confirm if Kamailio supports Netann protocol ?

2)      If not, how to route the INVITE with the correct R-URI format ?

Thanks in advance.

PatriceB

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 

Daniel-Constantin Mierla - http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu

Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.