Re: Не могу победить SIP

От: Aleksey Podmarev <CGatePro_at_mx_ru>
Дата: Tue 28 Oct 2008 - 15:01:26 MSK

On Tue, 2008-10-28 at 13:22 +0300, Valera V.Harseko wrote:
> Трабл в том, что CGP не понимает вида контакта 192.168.1.230 т.е. не может
> разрешить в маршрутизаторе запись Access:192.168.1.230
> Хотя записи вида user@192.168.1.230 разрешает как пользователь user на
> 192.168.1.230
>
> Подхода 2:
>
> 1. Ковырять cisco чтобы оно регистрировалось на cgp как user@192.168.1.230 а
&g
t; не 192.168.1.230
>
https://support.communigate.com/tickets/kb_article.php?ref=9663-YPFK-7527
> 2. Прописать на cgp чтобы он сам регистрировался на cisco как на удаленном
> шлюзе

>
https://support.communigate.com/tickets/kb_article.php?ref=9112-RSLV-4739
>

Пошел по первому пути - прописал вот так:

voice-port 0/1/0
 supervisory disconnect dualtone mid-call  input gain 11
 output attenuation -5
 no comfort-noise
 connection plar 200
 station-id name line1
 station-id number 200

легче не стало, хотя ROUTER больше не ругается: 14:52:55.619 2 SIPDATA-000013 inp: req [0.0.0.0]:5060 <- udp[192.168.1.230]:54950 INVITE(1050 bytes) sip:200@mail.mydom.ru:5060

14:52:55.619 4 SIPDATA-000013 Hash=426310872
14:52:55.619 4 SIPS-000008 enqueued
14:52:55.619 2 SIPS-000008 [000013] INVITE sip:200@mail.mydom.ru:5060 from udp[192.168.1.230]:54950
14:52:55.619 2 SIPDATA-000013 created SIPS-000008
14:52:55.620 2 SIPDATA-000014 out: rsp [0.0.0.0]:5060 -> udp[192.168.1.230]:5060 100-INVITE(293 bytes)
14:52:55.620 2 SIPS-000008 [000014] 100-INVITE(trying) sent to udp[192.168.1.230]:5060
14:52:55.620 4 SIGNAL-000130 enqueued
14:52:55.620 2 SIPS-000008 created SIGNAL-000130
14:52:55.620 2 SIGNAL-000130 SIPS-000008: INVITE sip:200@mail.mydom.ru:5060
14:52:55.620 4 SIGNAL-000130 AOR added: sip:200@mail.mydom.ru:5060
14:52:55.620 4 SIGNAL-000130 applying server rules
14:52:55.620 2 SIGNAL-000130 INVITE sip:200@mail.mydom.ru:5060 via sip:200@mail.mydom.ru:5060
14:52:55.642 2 DIALOG-000007 created(authInp)
14:52:55.643 2 DIALOG-000007 callee set: pbx@mx1.mail.mydom.ru
14:52:55.643 4 SIGNAL-000130 applying Account rules
14:52:55.643 4 SIGNALRULE-000130 rule(PBX Center starter) conditions met
14:52:55.643 2 SIGNALRULE-000130 rule(PBX Center starter): redirected
14:52:55.643 4 SIGNAL-000130 AOR added: sip:pbx#pbx@mx1.mail.mydom.ru
14:52:55.643 2 SIGNAL-000130 redirected by Rules
14:52:55.643 2 SIGNAL-000130 INVITE sip:pbx#pbx@mx1.mail.mydom.ru via sip:pbx#pbx@mx1.mail.mydom.ru
14:52:55.643 4 PBXLEG-000094 enqueued
14:52:55.643 2 PBXLEG-000094 'pbx' created for pbx@mx1.mail.mydom.ru
14:52:55.643 4 PBXLEG-000094 INVITE request received
14:52:55.643 2 SIGNAL-000130 {2} sent to NODE-000094: INVITE sip:pbx#pbx@mx1.mail.mydom.ru
14:52:55.643 2 DIALOG-000008 created as DIALOG-000007 copy(copy)
14:52:55.643 2 DIALOG-000008 enqueued
14:52:55.643 2 PBXLEG-000094 DIALOG-000008(inp) started with 200@192.168.1.230(sip:200@192.168.1.230:5060)(canUpdate)(canTransfer)
14:52:55.643 2 PBXLEG-000094 session refresh=300(active)
14:52:55.643 4 PBXLEG-000094 remote SDP set: peer
14:52:55.643 4 PBXLEG-000094 signalling completed(init)
14:52:55.643 2 PBXLEG-000094 started(Main)
14:52:55.644 2 MEDIA-000004 created(44444448) for PBXLEG-000094, audio port [0.0.0.0]:60000
14:52:55.644 1 MEDIA-000004 SDP cannot be set. Error Code=No supported audio codec found
14:52:55.644 1 PBXLEG-000094 failed to init Media Channel with saved SDP. Error Code=No supported audio codec found
14:52:55.644 4 PBXLEG-000094 MEDIA-000004 released
14:52:55.644 2 MEDIA-000004 processor started
14:52:55.644 4 MEDIA-000004 closing
14:52:55.750 2 MEDIA-000004 processor finished
14:52:55.847 2 MEDIA-000004 released
14:52:55.847 4 PBXLEG-000094 session timer refreshed
14:52:55.847 2 SIGNAL-000130 488 received from NODE-000094
14:52:55.847 2 PBXLEG-000094 killing DIALOG-000008
14:52:55.847 4 SIGNAL-000130 collected code=488
14:52:55.847 2 DIALOG-000008 dequeued(kill)
14:52:55.847 2 SIGNAL-000130 updating DIALOG-000007 on 488-response
14:52:55.847 2 DIALOG-000008 released
14:52:55.847 2 PBXLEG-000094 program stopped
14:52:55.847 4 PBXLEG-000094 leg finishing
14:52:55.847 4 PBXLEG-000094 dequeued
14:52:55.847 4 PBXLEG-000094 closing
14:52:55.848 2 ACCOUNT(pbx) inp call failed. Error Code=No supported audio codec found
14:52:55.874 2 SIGNAL-000130 488 relaying
14:52:55.874 4 SIGNAL-000130 dequeued
14:52:55.874 2 SIPDATA-000015 out: rsp [0.0.0.0]:5060 -> udp[192.168.1.230]:5060 488-INVITE(330 bytes)
14:52:55.874 2 SIPS-000008 [000015] 488-INVITE(final) sent to udp[192.168.1.230]:5060
14:52:55.874 4 SIPS-000008 completed
14:52:55.887 2 SIPDATA-000016 inp: req [0.0.0.0]:5060 <- udp[192.168.1.230]:5060 ACK(356 bytes) sip:200@mail.mydom.ru:5060
14:52:55.887 4 SIPDATA-000016 Hash=426310872
14:52:55.887 2 SIPDATA-000016 sent to SIPS-000008
14:52:55.887 2 SIPS-000008 [000016] confirmed: ACK received
14:52:59.160 2 SMTPI-000646(uisnet1.mydom.ru) [720754] received encrypted, 1740 bytes
14:53:00.001 4 SIPS-000008 I-timer over
14:53:00.002 4 SIPS-000008 dequeued
14:53:00.002 2 DIALOG-000007 released

> -----Original Message-----
> From: CommuniGate Pro Russian Discussions [mailto:CGatePro@mx.ru]
> Sent: Tuesday, October 28, 2008 1:01 PM
> To: CommuniGate Pro Russian Discussions
> Subject: Re: [CGP] Не могу победить SIP
>
> On Tue, 2008-10-28 at 12:52 +0300, Valera V.Harseko wrote:
> > У вас устройство прописано как External Gateway ?
>
> Это какое устройство имеется ввиду? Где прописано? Нет, наверное, не
> прописано. Я не очень понимаю, о чем речь.
>
> > Добавьте в маршрутизацию:
> > S:<mycontact> = gatewayincoming{pbx,"mixer"}#pbx;
> >
> > Где mycontact это запись поля Contact: шлюза
>
> Шлюз - это cisco? Там нет поля "Contact:"...
>
> Что-то я совсем запутался. :-(
>

-- 
С уважением,
Алексей Подмарев
Получено Tue Oct 28 12:01:34 2008

Этот архив был сгенерирован hypermail 2.1.8 : Tue 28 Oct 2008 - 16:15:16 MSK