Hello
I am using Linksys spa 921 to talk to openser. The problem I am having is that when the phone gets a 401 Unauthorized msg from Openser during REGISTER, instead of re-register with digest, it sends back another Unauthorized msg to openser. Does anyone know when this is happening?
U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" sip:1005@43.34.342.12. Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" sip:1005@192.168.1.101:5060;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. .
U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" sip:1005@43.34.342.12. Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" sip:1005@192.168.1.101:5060;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. .
U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
Any suggestion to solving this problem will be great.
JB
Take a look at the port the REGISTER is coming from (16309) and where openser is sending the challenge to (5060). I would bet that the router at 43.34.342.12 is not forwarding back the 401 so the SPA does not see it and it keeps retransmiting the original REGISTER as it hadn't reached the server.
I would recommend that you check the NAT related stuff in your openser script to solve this issue.
Hope it helps,
Smauel.
2008/7/8, Juan Backson juanbackson@gmail.com:
Hello
I am using Linksys spa 921 to talk to openser. The problem I am having is that when the phone gets a 401 Unauthorized msg from Openser during REGISTER, instead of re-register with digest, it sends back another Unauthorized msg to openser. Does anyone know when this is happening?
U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" sip:1005@43.34.342.12. Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" sip:1005@192.168.1.101:5060;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. .
U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" sip:1005@43.34.342.12. Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" sip:1005@192.168.1.101:5060;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. .
U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" sip:1005@43.34.342.12;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12
;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb.
Call-ID: 6e601902-41d31f68@192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. .
Any suggestion to solving this problem will be great.
JB
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
El Tuesday 08 July 2008 10:43:31 Juan Backson escribió:
Hello
I am using Linksys spa 921 to talk to openser. The problem I am having is that when the phone gets a 401 Unauthorized msg from Openser during REGISTER, instead of re-register with digest, it sends back another Unauthorized msg to openser. Does anyone know when this is happening?
U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028.
U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized.
Configure your Linkssy to add "rport" parameter to Via header, or use "force_rport()" in your OpenSer script.
-
Iñaki Baz Castillo -
Juan Backson -
samuel