Hi everybody!
I want to use the Path support in the module registrar. So I set, in my configuration file, the following parameters:
loadmodule "/usr/lib/openser/modules/registrar.so"
modparam("registrar", "use_path", 1) modparam("registrar", "path_mode", 2)
I expected that OpenSER rejects all REGISTER requests that not have the Path support indicated but in fact it accepts the REGISTER and reply with a 200 OK instead of a 420 - Bad Extension.
I am using OpenSER 1.1.0 with TLS support in a debian package.
Does anyone have some experience with this module?
Thanks
Greg
Gregoire wrote:
I expected that OpenSER rejects all REGISTER requests that not have the Path support indicated but in fact it accepts the REGISTER and reply with a 200 OK instead of a 420 - Bad Extension.
Can you please post the dump using "ngrep -W byline" of such a register and the reply?
Andy
Andreas Granig wrote:
Gregoire wrote:
I expected that OpenSER rejects all REGISTER requests that not have the Path support indicated but in fact it accepts the REGISTER and reply with a 200 OK instead of a 420 - Bad Extension.
Can you please post the dump using "ngrep -W byline" of such a register and the reply?
Andy
Here is my output:
U 84.74.224.128:1024 -> 62.220.134.41:5060 REGISTER sip:voip.voxip.ch SIP/2.0. From: sip:portable@voip.voxip.ch. To: sip:portable@voip.voxip.ch. Max-Forwards: 70. Call-ID: 145457913@192.168.40.2. CSeq: 521 REGISTER. Contact: sip:portable@192.168.40.2:5060;transport=UDP;+sip.p2t="true";expires=60. User-Agent: Minisip. Via: SIP/2.0/UDP 192.168.40.2:5060;branch=z9hG4bK1541562582. Content-Length: 0. .
# U 62.220.134.41:5060 -> 84.74.224.128:1024 SIP/2.0 401 Unauthorized. From: sip:portable@voip.voxip.ch. To: sip:portable@voip.voxip.ch;tag=daa00445f05d147eeec3a38791880472.a24f. Call-ID: 145457913@192.168.40.2. CSeq: 521 REGISTER. Via: SIP/2.0/UDP 192.168.40.2:5060;branch=z9hG4bK1541562582;rport=1024;received=84.74.224.128. WWW-Authenticate: Digest realm="voxip.ch", nonce="455c3a4bba9de2eed163a5311fc8e434adaa826e". Server: OpenSer (1.1.0-tls (i386/linux)). Content-Length: 0. Warning: 392 62.220.134.41:5060 "Noisy feedback tells: pid=27152 req_src_ip=84.74.224.128 req_src_port=1024 in_uri=sip:voip.voxip.ch out_uri=sip:voip.voxip.ch via_cnt==1". .
# U 84.74.224.128:1024 -> 62.220.134.41:5060 REGISTER sip:voip.voxip.ch SIP/2.0. From: sip:portable@voip.voxip.ch. To: sip:portable@voip.voxip.ch. Max-Forwards: 70. Call-ID: 145457913@192.168.40.2. CSeq: 522 REGISTER. Contact: sip:portable@192.168.40.2:5060;transport=UDP;expires=60. User-Agent: Minisip. Authorization: Digest algorithm="MD5", username="portable", realm="voxip.ch", nonce="455c3a4bba9de2eed163a5311fc8e434adaa826e", uri="192.168.40.2", response="03dec410ca2aa6b8cf2aebce83ab0385". Via: SIP/2.0/UDP 192.168.40.2:5060;branch=z9hG4bK1642104892. Content-Length: 0. .
#U 62.220.134.41:5060 -> 84.74.224.128:1024 SIP/2.0 200 OK. From: sip:portable@voip.voxip.ch. To: sip:portable@voip.voxip.ch;tag=daa00445f05d147eeec3a38791880472.a4c0. Call-ID: 145457913@192.168.40.2. CSeq: 522 REGISTER. Via: SIP/2.0/UDP 192.168.40.2:5060;branch=z9hG4bK1642104892;rport=1024;received=84.74.224.128. Contact: sip:portable@192.168.40.2:5060;transport=UDP;expires=60;received="sip:84.74.224.128:1024". Server: OpenSer (1.1.0-tls (i386/linux)). Content-Length: 0. Warning: 392 62.220.134.41:5060 "Noisy feedback tells: pid=27144 req_src_ip=84.74.224.128 req_src_port=1024 in_uri=sip:voip.voxip.ch out_uri=sip:voip.voxip.ch via_cnt==1". .
Thanks for you help
Greg
Gregoire wrote:
Here is my output:
<snip>
U 84.74.224.128:1024 -> 62.220.134.41:5060 REGISTER sip:voip.voxip.ch SIP/2.0. From: sip:portable@voip.voxip.ch. To: sip:portable@voip.voxip.ch. Max-Forwards: 70. Call-ID: 145457913@192.168.40.2. CSeq: 522 REGISTER. Contact: sip:portable@192.168.40.2:5060;transport=UDP;expires=60. User-Agent: Minisip. Authorization: Digest algorithm="MD5", username="portable", realm="voxip.ch", nonce="455c3a4bba9de2eed163a5311fc8e434adaa826e", uri="192.168.40.2", response="03dec410ca2aa6b8cf2aebce83ab0385". Via: SIP/2.0/UDP 192.168.40.2:5060;branch=z9hG4bK1642104892. Content-Length: 0.
Ok, but there's no Path-Header, so you get a 200-OK. If there would be a Path-Header, but no "Supported: path", then you'd get a "420 - Bad Extension".
path_mode=2 indicates that if you use Path, you also have to use "Supported: path".
Andy
-
Andreas Granig -
Gregoire