Registrar is some Nortel software... At first bad trace where uac_registrant can't register and state=6 with message in syslog "Wrong credentials for":
---------------------------- 123.123.123.123:5099 -> 222.222.222.222:5060 REGISTER sip:registrant.com SIP/2.0. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK5c4e.fdef4832.0. To: sip:[email protected]. From: <sip:[email protected]>;tag=d9430. CSeq: 1 REGISTER. Call-ID: 74f547c35287d7d9b6e874f6e72. Max-Forwards: 70. Content-Length: 0. User-Agent: OpenSIPS (1.7.2-notls (x86_64/linux)). Contact: <sip:[email protected]:5099>;expires=160. . # U 222.222.222.222:5060 -> 123.123.123.123:5099 SIP/2.0 100 Trying. From: <sip:[email protected]>;tag=d9430. To: <sip:[email protected]>. Call-ID: 74f547c35287d7d9b6e874f6e72. CSeq: 1 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK5c4e.fdef4832.0. Content-Length: 0. . # U 222.222.222.222:5060 -> 123.123.123.123:5099 SIP/2.0 407 Proxy Authentication Required. From: <sip:[email protected]>;tag=d9430. To: <sip:[email protected]>;tag=1292017548. Call-ID: 74f547c35287d7d9b6e874f6e72. CSeq: 1 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK5c4e.fdef4832.0. supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join. proxy-authenticate: Digest realm="Realm",nonce="MTMzNzg0MTg5OTIwM2Y2YTFiN2JiMGUyNmQ0ZmM4MTAyMTBkYjIyNDI5NzJk",stale=false,algorithm=MD5,qop="auth,auth-int". Content-Length: 0. . # U 123.123.123.123:5099 -> 222.222.222.222:5060 REGISTER sip:registrant.com SIP/2.0. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK2c4e.950290a6.0. To: sip:[email protected]. From: <sip:[email protected]>;tag=d9430. CSeq: 2 REGISTER. Call-ID: 74f547c35287d7d9b6e874f6e72. Max-Forwards: 70. Content-Length: 0. User-Agent: OpenSIPS (1.7.2-notls (x86_64/linux)). Contact: <sip:[email protected]:5099>;expires=160. Proxy-Authorization: Digest username="username1", realm="Realm", nonce="MTMzNzg0MTg5OTIwM2Y2YTFiN2JiMGUyNmQ0ZmM4MTAyMTBkYjIyNDI5NzJk", uri="sip:registrant.com", qop=auth, nc=00000001, cnonce="1085969230", response="0cffcc3c86879b06b7653d8b824c625d", algorithm=MD5. . # U 222.222.222.222:5060 -> 123.123.123.123:5099 SIP/2.0 100 Trying. From: <sip:[email protected]>;tag=d9430. To: <sip:[email protected]>. Call-ID: 74f547c35287d7d9b6e874f6e72. CSeq: 2 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK2c4e.950290a6.0. Content-Length: 0. . # U 222.222.222.222:5060 -> 123.123.123.123:5099 SIP/2.0 407 Proxy Authentication Required. From: <sip:[email protected]>;tag=d9430. To: <sip:[email protected]>;tag=1930837832. Call-ID: 74f547c35287d7d9b6e874f6e72. CSeq: 2 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5099;branch=z9hG4bK2c4e.950290a6.0. supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join. proxy-authenticate: Digest realm="Realm",nonce="MTMzNzg0MTg5OTIwM2Y2YTFiN2JiMGUyNmQ0ZmM4MTAyMTBkYjIyNDI5NzJk",stale=false,algorithm=MD5,qop="auth,auth-int". Content-Length: 0. ---------------------------- Second trace shows as Asterisk successful register. U 123.123.123.123:5060 -> 222.222.222.222:5060 REGISTER sip:registrant.com SIP/2.0. Via: SIP/2.0/UDP 123.123.123.123:5060;branch=z9hG4bK2ca386fa;rport. Max-Forwards: 70. From: <sip:[email protected]>;tag=as336b2c86. To: <sip:[email protected]>. Call-ID: [email protected]. CSeq: 104 REGISTER. User-Agent: Asterisk PBX 1.8.8.1-1digium1~squeeze. Authorization: Digest username="username1", realm="Realm", algorithm=MD5, uri="sip:registrant.com", nonce="MTMzNzg0MjAyMDMwMzhiZmEwODAxZmFlOTg2ZGJiNTFjYzVmYzgwMTE0Mjdj", response="8d11c83d7409ec062346f4c7ccf8ffed", qop=auth, cnonce="104d4c74", nc=00000002. Expires: 60. Contact: <sip:[email protected]:5060>. Content-Length: 0. . # U 222.222.222.222:5060 -> 123.123.123.123:5060 SIP/2.0 100 Trying. From: <sip:[email protected]>;tag=as336b2c86. To: <sip:[email protected]>. Call-ID: [email protected]. CSeq: 104 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5060;rport=5060;branch=z9hG4bK2ca386fa. Content-Length: 0. . # U 222.222.222.222:5060 -> 123.123.123.123:5060 SIP/2.0 200 Registration Successful. From: "username1 username1"<sip:[email protected]>;tag=as336b2c86. To: <sip:[email protected]>;tag=2120312459. Call-ID: [email protected]. CSeq: 104 REGISTER. Via: SIP/2.0/UDP 123.123.123.123:5060;rport=5060;branch=z9hG4bK2ca386fa. contact: <sip:[email protected]:5060 >;expires=60,<sip:[email protected]:62374 ;rinstance=c18b3810debbb4db;transport=UDP>;expires=1320. supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join. Content-Length: 0. 2012/5/24 Ovidiu Sas <[email protected]> > Can you provide the db records for the two cases along with ngrep traces? > The "To" header is not part of the authentication process. What kind > of registrar are you using? > > Regards, > Ovidiu Sas > > -- > VoIP Embedded, Inc. > http://www.voipembedded.com > > On Thu, May 24, 2012 at 3:25 AM, [email protected] > <[email protected]> wrote: > > Hi, all! > > > > I think i found some interconection trouble, if i send REGISTER: > > > > ... > > From: <sip:[email protected]>;tag=as336b2c86. > > To: <sip:[email protected]>. > > ... > > > > And register is OK. > > > > When i send REGISTER: > > .... > > To: sip:[email protected]. > > From: <sip:[email protected]>;tag=f046e. > > ... > > And get message "Wrong Credentials for" in syslog. > > > > May be problem with generated TO header by uac_registrant module? > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
