Hello. We have an issue with REGISTER to Provider. When Provider answers 401 Kamailio don't send any REGISTER with digest auth
IP ourservice.com.5068 > provider.dev.5060: UDP, length 468 E...U...@.3' ..............AREGISTER sip:provider.dev SIP/2.0 Via: SIP/2.0/UDP ourservice.com:5068 ;branch=z9hG4bK4238.45a4a626000000000000000000000000.0 To: sip:login@provider.dev From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 CSeq: 10 REGISTER Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.3.0-dev5 (x86_64/linux)) Contact: sip:login@ourservice.com:5068 Expires: 360
IP provider.dev.5060 > ourservice.com.5068: UDP, length 572 E..XC...-.W..... ........DkJSIP/2.0 401 Unauthorized Via: SIP/2.0/UDP ourservice.com:5068 ;branch=z9hG4bK4238.45a4a626000000000000000000000000.0;received=23.100.24.250 From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 To: sip:login@provider.dev;tag=as6ad61d4a Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com CSeq: 10 REGISTER Server: FastTel SoftSwitch Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="provider.dev", nonce="63fc6951" Content-Length: 0
Hello,
does that happen in all cases or just for some records? Can you rung with debug=3 and check the syslog messages for what happens at that moment when 401 is processed?
Cheers, Daniel
On 30/04/15 11:37, Yuriy Gorlichenko wrote:
Hello. We have an issue with REGISTER to Provider. When Provider answers 401 Kamailio don't send any REGISTER with digest auth
IP ourservice.com.5068 > provider.dev.5060: UDP, length 468 E...U...@.3' ..............AREGISTER sip:provider.dev SIP/2.0 Via: SIP/2.0/UDP ourservice.com:5068;branch=z9hG4bK4238.45a4a626000000000000000000000000.0 To: sip:login@provider.dev From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 CSeq: 10 REGISTER Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com mailto:1b3f9f5d5822eca2-16804@ourservice.com Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.3.0-dev5 (x86_64/linux)) Contact: <sip:login@ourservice.com:5068 http://sip:login@ourservice.com:5068> Expires: 360
IP provider.dev.5060 > ourservice.com.5068: UDP, length 572 E..XC...-.W..... ........DkJSIP/2.0 401 Unauthorized Via: SIP/2.0/UDP ourservice.com:5068;branch=z9hG4bK4238.45a4a626000000000000000000000000.0;received=23.100.24.250 From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 To: sip:login@provider.dev;tag=as6ad61d4a Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com mailto:1b3f9f5d5822eca2-16804@ourservice.com CSeq: 10 REGISTER Server: FastTel SoftSwitch Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="provider.dev", nonce="63fc6951" Content-Length: 0
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
This happens only with one trunk. We also have plivo trunks and it works fine.
Syslog show nothing when this message comes
Started with debug mode and saw that realms didn't mach. Sorry for stupid questions. All works fine.
2015-04-30 13:24 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
does that happen in all cases or just for some records? Can you rung with debug=3 and check the syslog messages for what happens at that moment when 401 is processed?
Cheers, Daniel
On 30/04/15 11:37, Yuriy Gorlichenko wrote:
Hello. We have an issue with REGISTER to Provider. When Provider answers 401 Kamailio don't send any REGISTER with digest auth
IP ourservice.com.5068 > provider.dev.5060: UDP, length 468 E...U...@.3' ..............AREGISTER sip:provider.dev SIP/2.0 Via: SIP/2.0/UDP ourservice.com:5068 ;branch=z9hG4bK4238.45a4a626000000000000000000000000.0 To: sip:login@provider.dev From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 CSeq: 10 REGISTER Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.3.0-dev5 (x86_64/linux)) Contact: sip:login@ourservice.com:5068 Expires: 360
IP provider.dev.5060 > ourservice.com.5068: UDP, length 572 E..XC...-.W..... ........DkJSIP/2.0 401 Unauthorized Via: SIP/2.0/UDP ourservice.com:5068 ;branch=z9hG4bK4238.45a4a626000000000000000000000000.0;received=23.100.24.250 From: sip:login@provider.dev;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 To: sip:login@provider.dev;tag=as6ad61d4a Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com CSeq: 10 REGISTER Server: FastTel SoftSwitch Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="provider.dev", nonce="63fc6951" Content-Length: 0
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com
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
On 30/04/15 12:46, Yuriy Gorlichenko wrote:
This happens only with one trunk. We also have plivo trunks and it works fine.
Syslog show nothing when this message comes
Started with debug mode and saw that realms didn't mach. Sorry for stupid questions. All works fine.
Note that if you don't set the realm value in database, then the one from 401 is used. So, unless you want to enforce the realm, you better leave it empty in the database.
Cheers, Daniel
2015-04-30 13:24 GMT+03:00 Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com>:
Hello, does that happen in all cases or just for some records? Can you rung with debug=3 and check the syslog messages for what happens at that moment when 401 is processed? Cheers, Daniel On 30/04/15 11:37, Yuriy Gorlichenko wrote:
Hello. We have an issue with REGISTER to Provider. When Provider answers 401 Kamailio don't send any REGISTER with digest auth IP ourservice.com.5068 > provider.dev.5060: UDP, length 468 E...U...@.3 <mailto:E...U...@.3>' ..............AREGISTER sip:provider.dev SIP/2.0 Via: SIP/2.0/UDP ourservice.com:5068;branch=z9hG4bK4238.45a4a626000000000000000000000000.0 To: <sip:login@provider.dev> From: <sip:login@provider.dev>;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 CSeq: 10 REGISTER Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com <mailto:1b3f9f5d5822eca2-16804@ourservice.com> Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.3.0-dev5 (x86_64/linux)) Contact: <sip:login@ourservice.com:5068 <http://sip:login@ourservice.com:5068>> Expires: 360 IP provider.dev.5060 > ourservice.com.5068: UDP, length 572 E..XC...-.W..... ........DkJSIP/2.0 401 Unauthorized Via: SIP/2.0/UDP ourservice.com:5068;branch=z9hG4bK4238.45a4a626000000000000000000000000.0;received=23.100.24.250 From: <sip:login@provider.dev>;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 To: <sip:login@provider.dev>;tag=as6ad61d4a Call-ID: 1b3f9f5d5822eca2-16804@ourservice.com <mailto:1b3f9f5d5822eca2-16804@ourservice.com> CSeq: 10 REGISTER Server: FastTel SoftSwitch Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="provider.dev", nonce="63fc6951" Content-Length: 0 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users