Mailing List CGatePro-old@d07.ru Message #15910
From: "Varinov Nicolay" <CGatePro@mx.ru>
Subject: Вопрос по регистрации sip железяки на CGP
Date: Fri, 15 Jun 2007 20:40:54 +0400
To: CGatePro@mx.ru
День добрый ,

Есть  такая  железяка  на тестировании MTU от "Протея" представляет из
себя  24  аналоговых  порта с независимыми SIP пользователями и Eth на
SIP сервер. При попытке регистрации абонента на CGP выходит следующее:
не  регистрируется  по  причине  неправильного пароля. То что пароли в
настройках   как   железяки   так  и  CGP  одинаковые  сомневаться  не
приходится, проверялось.
Мня  смущает  то  что  нельзя  в  MTU имя пользователя для регистрации
прописать в виде "user@domain" только в виде "user", но пользователь в
главном домене.
Я  не  уверен  в прямости MTU, но хотелось бы понять что происходит не
так  и  с  кокой  стороны.  Хотя  пока  основное подозрение что MTU не
правильно  генерит  response  при  авторизации,  но  хотелось  бы быть
уверенным что проблема именно в этом.

Ниже лог двух попыток регистрации с MTU, CGP 5.1.9, Linux.


14:16:21.347 5 SIP [0.0.0.0]:5060 <- [192.168.20.100]:5060 inp(315): REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\n
14:16:21.355 2 SIPDATA-000930 inp: req [0.0.0.0]:5060 <- udp [192.168.20.100]:5060 REGISTER(315 bytes)
sip:sip2.sotcom.ru:5060
14:16:21.355 5 SIPDATA-000930 inp: REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0
14:16:21.355 5 SIPDATA-000930 inp: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:21.355 5 SIPDATA-000930 inp: To: <sip:5799@sip2.sotcom.ru:5060>
14:16:21.355 5 SIPDATA-000930 inp: From: <sip:5799@sip2.sotcom.ru:5060>
14:16:21.355 5 SIPDATA-000930 inp: Contact: <sip:5799@192.168.20.100:5060>
14:16:21.355 5 SIPDATA-000930 inp: Call-ID: 467262E35ABD500000000192.168.20.100
14:16:21.355 5 SIPDATA-000930 inp: CSeq: 100 REGISTER
14:16:21.356 5 SIPDATA-000930 inp: Max-Forwards: 70
14:16:21.356 5 SIPDATA-000930 inp: Content-Length: 0
14:16:21.356 5 SIPDATA-000930 inp: Expires: 3600
14:16:21.356 5 SIPDATA-000930 inp:
14:16:21.356 4 SIPDATA-000930 Hash=1907327095
14:16:21.356 2 SIPS-000580 enqueued
14:16:21.356 2 SIPDATA-000930 created SIPS-000580
14:16:21.356 2 SIPS-000580 [000930] REGISTER sip:sip2.sotcom.ru:5060 from udp [192.168.20.100]:5060
14:16:21.356 5 SIGNAL 000582: enqueued
14:16:21.356 2 SIGNAL-000582 enqueued
14:16:21.356 5 SIGNAL-000582 INITIAL posted
14:16:21.356 2 SIPS-000580 created SIGNAL-000582
14:16:21.356 5 SIGNAL(3) 000582: processing INITIAL
14:16:21.356 2 SIGNAL-000582 SIPS-000580: REGISTER sip:sip2.sotcom.ru:5060
14:16:21.356 4 SIGNAL-000582 AOR added: sip:sip2.sotcom.ru:5060
14:16:21.356 4 SIGNAL-000582 applying server rules
14:16:21.356 5 SIGNAL-000582 timeout set for 900 secs
14:16:21.356 2 SIGNAL-000582 REGISTER sip:sip2.sotcom.ru:5060 via sip:sip2.sotcom.ru:5060
14:16:21.356 4 SIGNAL-000582 processed locally
14:16:21.356 4 SIGNAL-000582 collected code=401
14:16:21.357 2 SIGNAL-000582 401 relaying
14:16:21.357 2 SIPDATA-000931 out: rsp [0.0.0.0]:5060 -> udp [192.168.20.100]:5060 401-REGISTER(414 bytes)
14:16:21.357 5 SIPDATA-000931 out: SIP/2.0 401 Authentication required
14:16:21.357 5 SIPDATA-000931 out: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:21.357 5 SIPDATA-000931 out: From: <sip:5799@sip2.sotcom.ru:5060>
14:16:21.357 5 SIPDATA-000931 out: To: <sip:5799@sip2.sotcom.ru:5060>;tag=482792AC
14:16:21.357 5 SIPDATA-000931 out: Call-ID: 467262E35ABD500000000192.168.20.100
14:16:21.357 5 SIPDATA-000931 out: CSeq: 100 REGISTER
14:16:21.357 5 SIPDATA-000931 out: WWW-Authenticate: Digest
realm="sip2.sotcom.ru",nonce="DB1EDE43C1A2299AF3A4",opaque="opaqueData",qop="auth",algorithm=MD5
14:16:21.357 5 SIPDATA-000931 out: Server: CommuniGatePro/5.1.9 _community_
14:16:21.357 5 SIPDATA-000931 out: Content-Length: 0
14:16:21.357 5 SIPDATA-000931 out:
14:16:21.357 5 SIP [0.0.0.0]:5060 -> [192.168.20.100]:5060 out(414): SIP/2.0 401 Authentication required\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\nFrom:
14:16:21.357 2 SIPS-000580 [000931] 401-REGISTER(final) sent to udp [192.168.20.100]:5060
14:16:21.357 4 SIPS-000580 completed
14:16:21.357 5 SIGNAL(3) 000582: killing
14:16:21.357 2 SIGNAL-000582 dequeued
14:16:21.544 5 SIP [0.0.0.0]:5060 <- [192.168.20.100]:5060 inp(570): REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\n
14:16:21.544 2 SIPDATA-000932 inp: req [0.0.0.0]:5060 <- udp [192.168.20.100]:5060 REGISTER(570 bytes)
sip:sip2.sotcom.ru:5060
14:16:21.544 5 SIPDATA-000932 inp: REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0
14:16:21.544 5 SIPDATA-000932 inp: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:21.544 5 SIPDATA-000932 inp: To: <sip:5799@sip2.sotcom.ru:5060>;tag=482792AC
14:16:21.544 5 SIPDATA-000932 inp: From: <sip:5799@sip2.sotcom.ru:5060>
14:16:21.544 5 SIPDATA-000932 inp: Contact: <sip:5799@192.168.20.100:5060>
14:16:21.544 5 SIPDATA-000932 inp: Call-ID: 467262E35ABD500000000192.168.20.100
14:16:21.544 5 SIPDATA-000932 inp: CSeq: 101 REGISTER
14:16:21.544 5 SIPDATA-000932 inp: Max-Forwards: 70
14:16:21.544 5 SIPDATA-000932 inp: Content-Length: 0
14:16:21.544 5 SIPDATA-000932 inp: Expires: 3600
14:16:21.544 5 SIPDATA-000932 inp: Authorization: Digest
username="5799",realm="sip2.sotcom.ru",nonce="DB1EDE43C1A2299AF3A4",uri="sip:sip2.sotcom.ru:5060",response="e3e8bbcec3be97ee04879cb7eb402c2e",algorithm=MD5,cnonce="00001f86",opaque=""opaqueData"",qop="auth",nc=00000001
14:16:21.545 5 SIPDATA-000932 inp:
14:16:21.545 4 SIPDATA-000932 Hash=1907327095
14:16:21.545 2 SIPS-000582 enqueued
14:16:21.545 2 SIPDATA-000932 created SIPS-000582
14:16:21.545 2 SIPS-000582 [000932] REGISTER sip:sip2.sotcom.ru:5060 from udp [192.168.20.100]:5060
14:16:21.545 1 ACCOUNT(5799) login(SIP) from [192.168.20.100] failed. Error Code=incorrect password
14:16:21.623 1 SIPS-000582 REGISTER authentication(DIGEST-HTTP) failed - ignoring. Error Code=incorrect password
14:16:21.623 5 SIGNAL 000584: enqueued
14:16:21.623 2 SIGNAL-000584 enqueued
14:16:21.623 5 SIGNAL-000584 INITIAL posted
14:16:21.623 5 SIGNAL(2) 000584: processing INITIAL
14:16:21.623 2 SIGNAL-000584 SIPS-000582: REGISTER sip:sip2.sotcom.ru:5060
14:16:21.623 4 SIGNAL-000584 AOR added: sip:sip2.sotcom.ru:5060
14:16:21.623 5 SIGNAL-000584 timeout set for 900 secs
14:16:21.623 2 SIGNAL-000584 REGISTER sip:sip2.sotcom.ru:5060 via sip:sip2.sotcom.ru:5060
14:16:21.623 4 SIGNAL-000584 processed locally
14:16:21.623 4 SIGNAL-000584 collected code=401
14:16:21.623 2 SIGNAL-000584 401 relaying
14:16:21.623 5 SIGNAL(2) 000584: killing
14:16:21.623 2 SIGNAL-000584 dequeued
14:16:21.623 2 SIPS-000582 created SIGNAL-000584
14:16:21.623 2 SIPDATA-000933 out: rsp [0.0.0.0]:5060 -> udp [192.168.20.100]:5060 401-REGISTER(291 bytes)
14:16:21.624 5 SIPDATA-000933 out: SIP/2.0 401 Authentication required
14:16:21.624 5 SIPDATA-000933 out: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:21.624 5 SIPDATA-000933 out: From: <sip:5799@sip2.sotcom.ru:5060>
14:16:21.624 5 SIPDATA-000933 out: To: <sip:5799@sip2.sotcom.ru:5060>;tag=482792AC
14:16:21.624 5 SIPDATA-000933 out: Call-ID: 467262E35ABD500000000192.168.20.100
14:16:21.624 5 SIPDATA-000933 out: CSeq: 101 REGISTER
14:16:21.624 5 SIPDATA-000933 out: Server: CommuniGatePro/5.1.9 _community_
14:16:21.624 5 SIPDATA-000933 out: Content-Length: 0
14:16:21.624 5 SIPDATA-000933 out:
14:16:21.624 5 SIP [0.0.0.0]:5060 -> [192.168.20.100]:5060 out(291): SIP/2.0 401 Authentication required\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\nFrom:
14:16:21.624 2 SIPS-000582 [000933] 401-REGISTER(final) sent to udp [192.168.20.100]:5060
14:16:21.624 4 SIPS-000582 completed
14:16:22.148 5 SIP [0.0.0.0]:5060 <- [192.168.20.100]:5060 inp(315): REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\n
14:16:22.148 2 SIPDATA-000934 inp: req [0.0.0.0]:5060 <- udp [192.168.20.100]:5060 REGISTER(315 bytes)
sip:sip2.sotcom.ru:5060
14:16:22.149 5 SIPDATA-000934 inp: REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0
14:16:22.149 5 SIPDATA-000934 inp: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:22.149 5 SIPDATA-000934 inp: To: <sip:5899@sip2.sotcom.ru:5060>
14:16:22.149 5 SIPDATA-000934 inp: From: <sip:5899@sip2.sotcom.ru:5060>
14:16:22.149 5 SIPDATA-000934 inp: Contact: <sip:5899@192.168.20.100:5060>
14:16:22.149 5 SIPDATA-000934 inp: Call-ID: 467262E4231CC00000001192.168.20.100
14:16:22.149 5 SIPDATA-000934 inp: CSeq: 100 REGISTER
14:16:22.149 5 SIPDATA-000934 inp: Max-Forwards: 70
14:16:22.149 5 SIPDATA-000934 inp: Content-Length: 0
14:16:22.149 5 SIPDATA-000934 inp: Expires: 3600
14:16:22.149 5 SIPDATA-000934 inp:
14:16:22.149 4 SIPDATA-000934 Hash=1072355150
14:16:22.149 2 SIPS-000584 enqueued
14:16:22.149 2 SIPS-000584 [000934] REGISTER sip:sip2.sotcom.ru:5060 from udp [192.168.20.100]:5060
14:16:22.149 5 SIGNAL 000586: enqueued
14:16:22.149 2 SIGNAL-000586 enqueued
14:16:22.149 5 SIGNAL-000586 INITIAL posted
14:16:22.149 2 SIPS-000584 created SIGNAL-000586
14:16:22.149 2 SIPDATA-000934 created SIPS-000584
14:16:22.149 5 SIGNAL(1) 000586: processing INITIAL
14:16:22.149 2 SIGNAL-000586 SIPS-000584: REGISTER sip:sip2.sotcom.ru:5060
14:16:22.149 4 SIGNAL-000586 AOR added: sip:sip2.sotcom.ru:5060
14:16:22.149 4 SIGNAL-000586 applying server rules
14:16:22.150 5 SIGNAL-000586 timeout set for 900 secs
14:16:22.150 2 SIGNAL-000586 REGISTER sip:sip2.sotcom.ru:5060 via sip:sip2.sotcom.ru:5060
14:16:22.150 4 SIGNAL-000586 processed locally
14:16:22.150 4 SIGNAL-000586 collected code=401
14:16:22.150 2 SIGNAL-000586 401 relaying
14:16:22.150 2 SIPDATA-000935 out: rsp [0.0.0.0]:5060 -> udp [192.168.20.100]:5060 401-REGISTER(414 bytes)
14:16:22.150 5 SIPDATA-000935 out: SIP/2.0 401 Authentication required
14:16:22.150 5 SIPDATA-000935 out: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:22.150 5 SIPDATA-000935 out: From: <sip:5899@sip2.sotcom.ru:5060>
14:16:22.150 5 SIPDATA-000935 out: To: <sip:5899@sip2.sotcom.ru:5060>;tag=57800122
14:16:22.150 5 SIPDATA-000935 out: Call-ID: 467262E4231CC00000001192.168.20.100
14:16:22.150 5 SIPDATA-000935 out: CSeq: 100 REGISTER
14:16:22.150 5 SIPDATA-000935 out: WWW-Authenticate: Digest
realm="sip2.sotcom.ru",nonce="DB1EDE43C1A2299AF3A4",opaque="opaqueData",qop="auth",algorithm=MD5
14:16:22.150 5 SIPDATA-000935 out: Server: CommuniGatePro/5.1.9 _community_
14:16:22.150 5 SIPDATA-000935 out: Content-Length: 0
14:16:22.150 5 SIPDATA-000935 out:
14:16:22.150 5 SIP [0.0.0.0]:5060 -> [192.168.20.100]:5060 out(414): SIP/2.0 401 Authentication required\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\nFrom:
14:16:22.150 2 SIPS-000584 [000935] 401-REGISTER(final) sent to udp [192.168.20.100]:5060
14:16:22.150 4 SIPS-000584 completed
14:16:22.150 5 SIGNAL(1) 000586: killing
14:16:22.150 2 SIGNAL-000586 dequeued
14:16:22.204 5 SIP [0.0.0.0]:5060 <- [192.168.20.100]:5060 inp(570): REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\n
14:16:22.204 2 SIPDATA-000936 inp: req [0.0.0.0]:5060 <- udp [192.168.20.100]:5060 REGISTER(570 bytes)
sip:sip2.sotcom.ru:5060
14:16:22.204 5 SIPDATA-000936 inp: REGISTER sip:sip2.sotcom.ru:5060 SIP/2.0
14:16:22.204 5 SIPDATA-000936 inp: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:22.204 5 SIPDATA-000936 inp: To: <sip:5899@sip2.sotcom.ru:5060>;tag=57800122
14:16:22.205 5 SIPDATA-000936 inp: From: <sip:5899@sip2.sotcom.ru:5060>
14:16:22.205 5 SIPDATA-000936 inp: Contact: <sip:5899@192.168.20.100:5060>
14:16:22.205 5 SIPDATA-000936 inp: Call-ID: 467262E4231CC00000001192.168.20.100
14:16:22.205 5 SIPDATA-000936 inp: CSeq: 101 REGISTER
14:16:22.205 5 SIPDATA-000936 inp: Max-Forwards: 70
14:16:22.205 5 SIPDATA-000936 inp: Content-Length: 0
14:16:22.205 5 SIPDATA-000936 inp: Expires: 3600
14:16:22.205 5 SIPDATA-000936 inp: Authorization: Digest
username="5899",realm="sip2.sotcom.ru",nonce="DB1EDE43C1A2299AF3A4",uri="sip:sip2.sotcom.ru:5060",response="85d16945840b0451d270dad7a60c22b7",algorithm=MD5,cnonce="0000222e",opaque=""opaqueData"",qop="auth",nc=00000001
14:16:22.205 5 SIPDATA-000936 inp:
14:16:22.205 4 SIPDATA-000936 Hash=1072355150
14:16:22.205 2 SIPS-000586 enqueued
14:16:22.205 2 SIPS-000586 [000936] REGISTER sip:sip2.sotcom.ru:5060 from udp [192.168.20.100]:5060
14:16:22.205 1 ACCOUNT(5899) login(SIP) from [192.168.20.100] failed. Error Code=incorrect password
14:16:22.206 2 SIPDATA-000936 created SIPS-000586
14:16:22.287 1 SIPS-000586 REGISTER authentication(DIGEST-HTTP) failed - ignoring. Error Code=incorrect password
14:16:22.287 5 SIGNAL 000588: enqueued
14:16:22.287 2 SIGNAL-000588 enqueued
14:16:22.287 5 SIGNAL-000588 INITIAL posted
14:16:22.287 2 SIPS-000586 created SIGNAL-000588
14:16:22.288 5 SIGNAL(3) 000588: processing INITIAL
14:16:22.288 2 SIGNAL-000588 SIPS-000586: REGISTER sip:sip2.sotcom.ru:5060
14:16:22.288 4 SIGNAL-000588 AOR added: sip:sip2.sotcom.ru:5060
14:16:22.288 5 SIGNAL-000588 timeout set for 900 secs
14:16:22.288 2 SIGNAL-000588 REGISTER sip:sip2.sotcom.ru:5060 via sip:sip2.sotcom.ru:5060
14:16:22.288 4 SIGNAL-000588 processed locally
14:16:22.288 4 SIGNAL-000588 collected code=401
14:16:22.288 2 SIGNAL-000588 401 relaying
14:16:22.288 2 SIPDATA-000937 out: rsp [0.0.0.0]:5060 -> udp [192.168.20.100]:5060 401-REGISTER(291 bytes)
14:16:22.288 5 SIPDATA-000937 out: SIP/2.0 401 Authentication required
14:16:22.288 5 SIPDATA-000937 out: Via: SIP/2.0/UDP 192.168.20.100:5060
14:16:22.288 5 SIPDATA-000937 out: From: <sip:5899@sip2.sotcom.ru:5060>
14:16:22.288 5 SIPDATA-000937 out: To: <sip:5899@sip2.sotcom.ru:5060>;tag=57800122
14:16:22.288 5 SIPDATA-000937 out: Call-ID: 467262E4231CC00000001192.168.20.100
14:16:22.288 5 SIPDATA-000937 out: CSeq: 101 REGISTER
14:16:22.288 5 SIPDATA-000937 out: Server: CommuniGatePro/5.1.9 _community_
14:16:22.288 5 SIPDATA-000937 out: Content-Length: 0
14:16:22.288 5 SIPDATA-000937 out:
14:16:22.288 5 SIP [0.0.0.0]:5060 -> [192.168.20.100]:5060 out(291): SIP/2.0 401 Authentication required\r\nVia:
SIP/2.0/UDP 192.168.20.100:5060\r\nFrom:
14:16:22.288 2 SIPS-000586 [000937] 401-REGISTER(final) sent to udp [192.168.20.100]:5060
14:16:22.288 4 SIPS-000586 completed
14:16:22.288 5 SIGNAL(3) 000588: killing
14:16:22.288 2 SIGNAL-000588 dequeued  

------------------------
С наилучшими пожеланиями
Николай Варинов.
------------------------

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster