Hello Andreas,
I run many times the sipsak and it is ok. Could you send me the logs in debug=7 and output of openser -V?
Daniel
On 08/09/07 00:32, Andreas Granig wrote:
Hi Daniel,
Very strange, since I currently tried a fresh version of latest 1.2 without any modifications, and it still doesn't work for me. After some tries, I get this errors:
unprocessed uri='sip:test@192.168.101.11;sw_domain=sipwise.com' domain='' ERROR: parse_uri: bad host in uri (error at char ERROR: parse_sip_msg_uri: bad uri sip:agranig@ xl_get_ruri: ERROR while parsing the R-URI processed uri='<null>' ERROR: parse_uri: bad host in uri (error at char ERROR: parse_sip_msg_uri: bad uri sip:agranig@
You can reproduce this easily using sipsak (just adapt the ruri-ip):
# sipsak -l 7060 -f /tmp/inv.txt \ -s sip:test@192.168.101.11;sw_domain=sipwise.com
The file /tmp/inv.txt contains:
INVITE sip:test@192.168.101.11;sw_domain=sipwise.com SIP/2.0 Via: SIP/2.0/UDP 192.168.101.11:7060;branch=z9hG4bKd65f.67a4c9a4.0 To: sip:test@sipwise.com From: sip:test@sipwise.com;tag=7AF24EE9-46BA33CF000A5188-B7C82BB0 CSeq: 10 INVITE Call-ID: 08BC2B20-46BA33CF000A51AC-B7C82BB0@192.168.101.11 Content-Length: 0 Contact: sip:default_en@192.168.101.11:7060 Content-Type: application/sdp Max-Forwards: 70 User-Agent: Sipwise media server
Regards, Andreas
Daniel-Constantin Mierla wrote:
Hello Andreas,
I have tested with trunk and latest 1.2 and everything went fine. Do you use the latest SVN version of branch 1.2? It was a fix of a similar issue some time ago.
Cheers, Daniel
On 08/08/07 10:14, Andreas Granig wrote:
Btw, forget the last log line "msg_uri: bad uri sip:user@", it sneaked in while copy&paste. Rest is ok.
Andreas Granig wrote:
Hi Bogdan,
No, the r-uri is definitely ok. Here's the real-world snipped and logging example. The snipped is placed as very first code in route[0]:
if(uri =~ ";sw_domain=.+") { xlog("L_INFO", "unprocessed uri='$ru'\n"); $var(swdom) = $(ru{uri.param,sw_domain}); xlog("L_INFO", "domain='$var(swdom)'\n"); $ru = "sip:" + $rU + "@" + $var(swdom); xlog("L_INFO", "processed uri='$ru'\n"); }This works well for ~5 times, then I get:
unprocessed uri='sip:agranig@192.168.101.11;sw_domain=sipwise.com' domain='' ERROR: parse_uri: bad host in uri (error at char ERROR: parse_sip_msg_uri: bad uri sip:agranig@ xl_get_ruri: ERROR while parsing the R-URI processed uri='<null>' msg_uri: bad uri sip:user@
Andreas
Bogdan-Andrei Iancu wrote:
Hi Andreas,
I rather suspect that there is a problem with the RURI you are trying to use. I guess you get the error for the first line ($var(mydom) = $(ru{uri.param,my_domain});), so can you check (xlog) what's the ruri before?
regards, bogdan
Andreas Granig wrote:
Hi,
At the top of my config I've put the following snippet for some SEMS routings:
if(uri =~ ";my_domain=.+") { $var(mydom) = $(ru{uri.param,my_domain}); xlog("L_INFO", "domain='$var(mydom)'\n"); $ru = "sip:" + $rU + "@" + $var(mydom); }It does nothing more than changing an r-uri "sip:user@domain;my_domain=otherdomain" to "sip:user@otherdomain". This works fine for some requests, but then it starts to complain:
xl_get_ruri: ERROR while parsing the R-URI domain='' ERROR: parse_uri: bad host in uri (error at char ERROR: parse_sip_msg_uri: bad uri sip:user@
So obviously the transformation $(ru{uri.param,my_domain}) doesn't return the parameter anymore, but it's present in the r-uri. After a restart it works again for some requests, then again stops working.
Any hints? Andreas
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users