All, I'm having a problem that I think has to do with Tel URIs.
Sometimes my provider sends me calls that look like this: INVITE sip:7135551637;rn=7135550099;npdi=yes@10.25.11.13:5060;dtg=HSTNSIPORIG02;user=phone
But sometimes I get calls that don't have NPDI set so I look it up and stick it on the URI (using URI add_param). The result looks like this:
INVITE sip:7135551637@10.25.11.13;npdi=yes@10.25.11.13:5060;rn=7135550099
They are complaining that all the optional parameters need to be located before the "@" sign. Now at first I jumped on that and said it was wrong, but in RFC 3261 it says: === SNIP === 19.1.6 Relating SIP URIs and tel URLs
When a tel URL (RFC 2806 [9]) is converted to a SIP or SIPS URI, the entire telephone-subscriber portion of the tel URL, including any parameters, is placed into the userinfo part of the SIP or SIPS URI.
Thus, tel:+358-555-1234567;postd=pp22 becomes
sip:+358-555-1234567;postd=pp22@foo.com;user=phone
or sips:+358-555-1234567;postd=pp22@foo.com;user=phone
not sip:+358-555-1234567@foo.com;postd=pp22;user=phone
or
sips:+358-555-1234567@foo.com;postd=pp22;user=phone ==========
So maybe these parameters DO in fact belong before the "@" sign..
So three questions.. 1. Do they belong before the "@" sign, what do you think? 2. how do I get ser to add these parameters before the "@" sign 3. Can ser interpret parameters before the "@" sign?
Thanks!