CGatePro: Re: не регистрируется на sip шлюзе

От: A.Pach <CGatePro_at_mx_ru>
Дата: Thu 29 Jan 2009 - 15:30:55 MSK

Не уверен но кажется проблема вот здесь
14:36:38.328 4 SIPC-066798 resolving
sip:88.87.64.228;maddr=88.87.64.228

On Thu, 29 Jan 2009 15:25:49 +0300
"Эдуард Ковалев" <CGatePro@mx.ru> wrote: Добрый день!

Имеем:

CommuniGatePro 5.2.10 win Находится за натом, порты проброшены: Внешний адрес NATа: 94.180.199.34 (Ограниченный конус по порту, Port:Случайный, SIP:Отсутствует, UPnP:Присутствует) Интерфейсы: 1-192.168.0.10, 2-0.0.0.0, 3-127.0.0.1, (DefIP:192.168.0.10, MSK:255.255.255.0, GW:192.168.0.1, DNS-OK, UDP5060-OK, TCP5060-OK) Задержка:51, Потери:0, Джиттер:43% - Качество Интернет канала отличное!

2. ТФОП провайдера с sip шлюзом (на том конце похоже AlterPSS) 3. используя eyebeam подключаемся и принимаем входящие звонки

Однако communigete регистрироваться отказывается (использую Установки
- Real-Time - SIP - Шлюзы, т.к. звонок нужно принять, а на том конце указать явно куда звонить возможности нет), логи:

14:36:38.328 5 SIP [0.0.0.0]:5060 <- [88.87.64.228]:5060 inp(409): SIP/2.0 401 Unauthorized\r\nVia: SIP/2.0/UDP 94.180.199.34:5060;branch=z9hG4bK6679
14:36:38.328 2 SIPDATA-155212 inp: rsp [0.0.0.0]:5060 <- udp[88.87.64.228]:5060 401-REGISTER(409 bytes)

  14:36:38.328 5 SIPDATA-155212 inp: SIP/2.0 401 Unauthorized
  14:36:38.328 5 SIPDATA-155212 inp: Via: SIP/2.0/UDP
94.180.199.34:5060;branch=z9hG4bK66796;rport
  14:36:38.328 5 SIPDATA-155212 inp: From:
<sip:xxxxxx@88.87.64.228>;tag=2C11EED5113CB763
  14:36:38.328 5 SIPDATA-155212 inp: To:

<sip:xxxxxx@88.87.64.228>;tag=88.87.64.225.5075-143105720-21997 14:36:38.328 5 SIPDATA-155212 inp: Call-ID: 7A22387F2F4562B0AB842AB00F09D876-3228995@kseon.ru 14:36:38.328 5 SIPDATA-155212 inp: CSeq: 5 REGISTER 14:36:38.328 5 SIPDATA-155212 inp: WWW-Authenticate: Digest realm="AlterPSS",nonce="b1d325c9151578d297ea8972f88b22ef",algorithm=MD5

  14:36:38.328 5 SIPDATA-155212 inp: Content-Length: 0
  14:36:38.328 5 SIPDATA-155212 inp:
  14:36:38.328 5 SIPC-066796 RESPONSE posted
  14:36:38.328 2 SIPDATA-155212 sent to SIPC-066796
  14:36:38.328 5 SIPC(1) 066796: processing RESPONSE
  14:36:38.328 2 SIPC-066796 [155212] 401-REGISTER received
  14:36:38.328 2 SIGNAL-129754 401 received from SIPC-066796
  14:36:38.328 2 SIGNAL-129754 401 relaying
  14:36:38.328 5 NODE-053100 FINAL posted
  14:36:38.328 5 NODE(1) 053100: processing FINAL
  14:36:38.328 2 NODE-053100 re-sending REGISTER sip:591965.sipgw
  14:36:38.328 5 NODE(1) 053100: idling
  14:36:38.328 2 SIGNAL-129756 NODE-053100: REGISTER sip:591965.sipgw
  14:36:38.328 2 ROUTER SMTP: 'xxxxxx@88.87.64.228' accepted: '591965'
at '[88.87.64.228]'
  14:36:38.328 2 SIGNAL-129756 REGISTER sip:591965.sipgw via

sip:591965.sipgw
14:36:38.328 2 ROUTER SIP: 'LoginPage@591965.sipgw' accepted: 'LoginPage@88.87.64.228' at '591965.sipgw'

  14:36:38.328 2 SIGNAL-129756 relaying to sip:88.87.64.228 via
sip:591965.sipgw
  14:36:38.328 4 SIPC-066798 enqueued
  14:36:38.328 5 SIPC-066798 INITIAL posted
  14:36:38.328 2 SIGNAL-129756 {1} sent to SIPC-066798: REGISTER

sip:88.87.64.228

  14:36:38.328 5 SIPC(3) 066798: processing INITIAL
  14:36:38.328 2 SIPC-066798 REGISTER sip:88.87.64.228
  14:36:38.328 4 SIPC-066798 resolving

sip:88.87.64.228;maddr=88.87.64.228

  14:36:38.328 4 SIPC-066798 trying: sip:88.87.64.228
  14:36:38.328 4 SIPC-066798 1 RRs added
  14:36:38.328 5 SIPC-066798 timeout set for 2 secs
  14:36:38.328 2 SIPDATA-155213 out: req [94.180.199.34]:5060 ->

udp[88.87.64.228]:5060 REGISTER(633 bytes) sip:88.87.64.228

  14:36:38.328 5 SIPDATA-155213 out: REGISTER sip:88.87.64.228 SIP/2.0
  14:36:38.328 5 SIPDATA-155213 out: Via: SIP/2.0/UDP
94.180.199.34:5060;branch=z9hG4bK66798;rport
  14:36:38.328 5 SIPDATA-155213 out: Path: <sip:94.180.199.34:5060;lr>
  14:36:38.328 5 SIPDATA-155213 out: Max-Forwards: 69
  14:36:38.328 5 SIPDATA-155213 out: From:
<sip:xxxxxx@88.87.64.228>;tag=2C11EED5113CB763

14:36:38.328 5 SIPDATA-155213 out: To: <sip:xxxxxx@88.87.64.228> 14:36:38.328 5 SIPDATA-155213 out: Call-ID: 7A22387F2F4562B0AB842AB00F09D876-3228995@kseon.ru

  14:36:38.328 5 SIPDATA-155213 out: Contact:
<sip:101@94.180.199.34;cgpgateway=591965>;expires=7
  14:36:38.328 5 SIPDATA-155213 out: CSeq: 6 REGISTER
  14:36:38.328 5 SIPDATA-155213 out: Expires: 10
  14:36:38.328 5 SIPDATA-155213 out: User-Agent:

CommuniGatePro-gateway/5.2.10
14:36:38.328 5 SIPDATA-155213 out: Authorization: Digest username="xxxxxx",realm="AlterPSS",nonce="b1d325c9151578d297ea8972f88b22ef",uri="sip:88.87.64.228",response="008b69a0d8bc55ebdd5dda6c0570ffcc",algorithm=MD5

  14:36:38.328 5 SIPDATA-155213 out: Content-Length: 0
  14:36:38.328 5 SIPDATA-155213 out:
  14:36:38.328 5 SIP [0.0.0.0]:5060 -> [88.87.64.228]:5060 out(633):

REGISTER sip:88.87.64.228 SIP/2.0\r\nVia: SIP/2.0/UDP 94.180.199.34:5060;branch=z9
14:36:38.328 2 SIPC-066798 [155213] REGISTER sip:88.87.64.228 sent [94.180.199.34]:5060 -> udp[88.87.64.228]:5060

  14:36:38.328 5 SIPC(3) 066798: enqueued (2 secs)
  14:36:38.328 4 SIPC-066796 completed
  14:36:38.328 5 SIPC-066796 timeout set for 5 secs
  14:36:38.328 5 SIPC(1) 066796: enqueued (5 secs)
  14:36:38.390 5 SIP [0.0.0.0]:5060 <- [88.87.64.228]:5060 inp(409):

SIP/2.0 401 Unauthorized\r\nVia: SIP/2.0/UDP 94.180.199.34:5060;branch=z9hG4bK6679
14:36:38.390 2 SIPDATA-155214 inp: rsp [0.0.0.0]:5060 <- udp[88.87.64.228]:5060 401-REGISTER(409 bytes)

  14:36:38.390 5 SIPDATA-155214 inp: SIP/2.0 401 Unauthorized
  14:36:38.390 5 SIPDATA-155214 inp: Via: SIP/2.0/UDP
94.180.199.34:5060;branch=z9hG4bK66798;rport
  14:36:38.390 5 SIPDATA-155214 inp: From:
<sip:xxxxxx@88.87.64.228>;tag=2C11EED5113CB763
  14:36:38.390 5 SIPDATA-155214 inp: To:

<sip:xxxxxx@88.87.64.228>;tag=88.87.64.225.5075-143105720-21997 14:36:38.390 5 SIPDATA-155214 inp: Call-ID: 7A22387F2F4562B0AB842AB00F09D876-3228995@kseon.ru 14:36:38.390 5 SIPDATA-155214 inp: CSeq: 6 REGISTER 14:36:38.390 5 SIPDATA-155214 inp: WWW-Authenticate: Digest realm="AlterPSS",nonce="be0b7741da1ef7ce8794e6a09d8973da",algorithm=MD5

  14:36:38.390 5 SIPDATA-155214 inp: Content-Length: 0
  14:36:38.390 5 SIPDATA-155214 inp:
  14:36:38.390 5 SIPC-066798 RESPONSE posted
  14:36:38.390 2 SIPDATA-155214 sent to SIPC-066798
  14:36:38.390 5 SIPC(2) 066798: processing RESPONSE
  14:36:38.390 2 SIPC-066798 [155214] 401-REGISTER received
  14:36:38.390 2 SIGNAL-129756 401 received from SIPC-066798
  14:36:38.390 2 SIGNAL-129756 401 relaying
  14:36:38.390 5 NODE-053100 FINAL posted
  14:36:38.390 5 NODE(2) 053100: processing FINAL
  14:36:38.390 2 NODE-053100 failed to register: 401 Unauthorized
  14:36:38.390 5 NODE-053100 timeout set for 180 secs
  14:36:38.390 5 NODE(2) 053100: enqueued (180 secs)
  14:36:38.390 4 SIPC-066798 completed
  14:36:38.390 5 SIPC-066798 timeout set for 5 secs
  14:36:38.390 5 SIPC(2) 066798: enqueued (5 secs)

Подскажите в какую сторону смотреть

  С Уважением,
  Эдуард Ковалев
  ЗАО "КСЕОН" г.Волгоград                   Получено Thu Jan 29 14:31:58 2009

Этот архив был сгенерирован hypermail 2.1.8 : Thu 29 Jan 2009 - 20:15:30 MSK