Меню

Emotion код ошибки 488

<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLi callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453086816 1453086817 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 30020 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 30020 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 33783cca-387a-1234-798b-002590e5052c
Found peer ‘M_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK0gvvQyg961BjS;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<————>
Scheduling destruction of SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK0gvvQyg961BjS
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=XaggZpUQ1m3vm
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as1471402a
Call-ID: 33783cca-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0

<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘33783cca-387a-1234-798b-002590e5052c’ Method: ACK

<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453097848 1453097849 IN IP4 193.27.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 18988 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 18988 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337bce93-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

<— Reliably Transmitting (NAT) to 19.2.41.21:5060 —>
SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP 19.2.41.21;branch=z9hG4bK1SNNSS1c4a24m;received=19.2.41.21;rport=5060
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Server: FPBX-2.8.1(1.8.20.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<————>
Scheduling destruction of SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:19.2.41.21:5060 —>
ACK sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK1SNNSS1c4a24m
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=Zv212cXyU6F2B
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>;tag=as4f0d2223
Call-ID: 337bce93-387a-1234-798b-002590e5052c
CSeq: 86222354 ACK
Content-Length: 0

<————->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘337bce93-387a-1234-798b-002590e5052c’ Method: ACK

<— SIP read from UDP:19.2.41.21:5060 —>
INVITE sip:s@1.2.3.4:5060;received=1.2.3.4:41394 SIP/2.0
Via: SIP/2.0/UDP 19.2.41.21;rport;branch=z9hG4bK22eeUmjg1KrQg
Route: <sip:s@1.2.3.4:41394>
Max-Forwards: 68
From: «+79262719630» <sip:89262719630@19.2.41.21>;tag=05Ut47D2rF6mQ
To: <sip:s@1.2.3.4:5060;received=1.2.3.4:41394>
Call-ID: 337f7865-387a-1234-798b-002590e5052c
CSeq: 86222354 INVITE
Contact: <sip:mod_sofia@19.2.41.21:5060>
User-Agent: MoLie callswitch1
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 373
X-FS-Support: update_display,send_info
Remote-Party-ID: «+79262719630» <sip:89262719630@19.2.41.21>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1453088024 1453088025 IN IP4 19.2.41.21
s=FreeSWITCH
c=IN IP4 19.2.41.21
t=0 0
m=audio 28812 RTP/AVP 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:30
m=audio 28812 RTP/AVP 8 0 18 101
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off — — — —
a=ptime:20
<————->
— (18 headers 16 lines) —
Sending to 19.2.41.21:5060 (NAT)
Using INVITE request as basis request — 337f7865-387a-1234-798b-002590e5052c
Found peer ‘Mo_010’ for ‘89262719630’ from 19.2.41.21:5060
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
Found RTP audio format 8
Found RTP audio format 0
Found RTP audio format 101
Found audio description format telephone-event for ID 101

Источник

488 Not acceptable here

 

  • В этой теме 7 ответов, 7 участников, последнее обновление 6 лет, 5 месяцев назад сделано bug0r.

Просмотр 8 сообщений — с 1 по 8 (из 8 всего)

  • Автор

    Сообщения

  • 25.06.2016 в 20:05

    #11850

    Сейчас стало 488 при любых звонках. Ещё пару часов назад всё работало. Снова чудит системка?

    25.06.2016 в 20:14

    #11851

    Снова чудит системка 🙁
    Надо снова копить нервные клетки и планировать обновление… Судя по рассылке в астериске исправили много-много ошибок. Сколько привнесли новых не сообщается.

    03.07.2016 в 09:24

    #11903

    Всё понятно 🙁
    Сейчас кстати опять то же самое. 488 и попытки звонков не отображаются в истории.

    17.08.2016 в 09:54

    #12325

    @demon
    488 при любых звонках CSipSimple. Сеть занята Zoiper.
    Учётные записи активны и подключены, судя по показаниям смартов и самого сервера.

    28.08.2016 в 18:13

    #12389

    У меня сегодня весь день ошибка 488.
    До этого сделал сброс телефона Гигасет.
    Не пойму, это только у меня такая ошибка или это проблема общая?

    28.08.2016 в 18:16

    #12390

    01.09.2016 в 17:10

    #12401

    Wi

    Участник

    У меня четыре раза 488, а на пятый раз звонок проходит.

    01.09.2016 в 19:31

    #12402

    У меня в то же самое время были аналогичные проблемы. В данный момент вроде все нормализовалось.

  • Автор

    Сообщения

Просмотр 8 сообщений — с 1 по 8 (из 8 всего)

  • Для ответа в этой теме необходимо авторизоваться.
Источник

Заказчик столкнулся с проблемой настройки IP телефона Fanvil X210 на аккаунт SIP-провайдера Билайн. Регистрация происходит успешно, но при попытке вызвать любой номер возвращается ошибка 488 Not Acceptable Here 

Согласно классификации, ошибки 4xx относятся к категории ошибок в полученном запросе:

  • 488 Codec Mismatch (нет шлюзов с поддержкой заказанного кодека)

Ситуация странная, поскольку рядом находится телефон Grandstream WP810 с тем же набором кодеков, настроенный на этот же сервер и исправно работающий. Оказалось, что Билайн не пропускал звонок из-за предложения телефона Fanvil X210 начать видео-вызов. Несмотря на то, что это не видеотелефон, он оснащен большим дисплеем и поддерживает прием видео-вызовов, то есть видеосвязь в одну сторону. Это удобно, когда телефон настраивается на работу с SIP-домофоном. Для корректной работы телефона Fanvil с Beeline требовалось отключить настройку «Метод набора по-умолчанию: Видео» и выбрать «Аудио»

Источник

Транзитный PBX обучили менять ответ линксиса 488 на 415 перед отправкой верхним людям… и опять ничерта не работает! Вот логи нескольких попыток (пробовал играться с кодеками, G711au, потом вообще отключал fax detect на линксисе) со стороны линксиса:

<151>[5060]STUN trying 0

192.168.193.200 27/10 16:11:57.375

<151>[8004]STUN trying 0

192.168.193.200 27/10 16:11:57.375

<151>[8005]STUN trying 0

192.168.193.200 27/10 16:11:57.375

<151>[8006]STUN trying 0

192.168.193.200 27/10 16:11:57.375

<151>[8007]STUN trying 0

192.168.193.200 27/10 16:11:57.375

<151>[5060]STUN trying 1

192.168.193.200 27/10 16:11:57.437

<151>[0:0]CC:STUN OK:c0a8c1c8->4d6ad70a, 5060->5060 8004->8004

192.168.193.200 27/10 16:11:57.437

<151>[0:0]AUD ALLOC CALL (port=8004)

192.168.193.200 27/10 16:11:57.437

<151>[0:0]RTP Rx Up

192.168.193.200 27/10 16:11:57.453

<159>[0]Off Hook

192.168.193.200 27/10 16:12:04.844

<151>CC:Connected

192.168.193.200 27/10 16:12:04.937

<151>[0:0]ENC INIT 0

192.168.193.200 27/10 16:12:04.937

<151>[0:0]RTP Tx Up (pt=0->c0a8c064:8000)

192.168.193.200 27/10 16:12:04.937

<151>[0:0]RTCP Tx Up

192.168.193.200 27/10 16:12:04.937

<151>[0:0]RTP Rx 1st PKT @8004(3)

192.168.193.200 27/10 16:12:05.031

<151>[0:0]DEC INIT 0

192.168.193.200 27/10 16:12:05.125

<151>[0]AUD:FAX Event=2

192.168.193.200 27/10 16:12:08.687

<151>[0:0]ENC INIT 0

192.168.193.200 27/10 16:12:08.687

<151>DLG:ReAllocCodecList

192.168.193.200 27/10 16:12:12.609

<159>[0]On Hook

192.168.193.200 27/10 16:12:54.281

<159>[0]FM Alert Stop RxTx (c=00241694;a=0)

192.168.193.200 27/10 16:12:54.297

<151>[0:0]AUD Rel Call

192.168.193.200 27/10 16:12:54.297

<151>DLG Terminated 294e1c

192.168.193.200 27/10 16:12:54.297

<151>Sess Terminated

192.168.193.200 27/10 16:12:54.297

<151>CC:Clean Up

192.168.193.200 27/10 16:13:28.094

<151>— OBJ POOL STAT —

192.168.193.200 27/10 16:13:28.094

<151>OP:RTPRXB = 96 ( 96 192) 192.168.193.200 27/10 16:13:28.094

<151>OP:RTPREB = 40 ( 40 48)

192.168.193.200 27/10 16:13:28.094

<151>OP:RTPTXB = 64 ( 64 108) 192.168.193.200 27/10 16:13:28.094

<151>OP:TIMEOU = 111 (120 52)

192.168.193.200 27/10 16:13:28.094

<151>OP:SIPCOR = 0 ( 1 28) 192.168.193.200 27/10 16:13:28.094

<151>OP:SIPCTS = 32 ( 32 1140)

192.168.193.200 27/10 16:13:28.094

<151>OP:SIPSTS = 32 ( 32 6620) 192.168.193.200 27/10 16:13:28.094

<151>OP:SIPAUS = 0 ( 8 588)

192.168.193.200 27/10 16:13:28.094

<151>OP:SIPDLG = 10 ( 10 148) 192.168.193.200 27/10 16:13:28.094

<151>OP:SIPSES = 12 ( 12 9776)

192.168.193.200 27/10 16:13:28.094

<151>OP:SIPREG = 3 ( 4 304) 192.168.193.200 27/10 16:13:28.109

<151>OP:SIPLIN = 0 ( 2 140)

192.168.193.200 27/10 16:13:28.109

<151>OP:SUBDLG = 2 ( 2 6436) 192.168.193.200 27/10 16:13:28.109

<151>OP:STUNTS = 16 ( 16 68)

192.168.193.200 27/10 16:13:28.109

<151>OP:XMNODE = 1024 (1024 112) 192.168.193.200 27/10 16:13:28.109

<151>

192.168.193.200 27/10 16:13:28.109

<159>fu:1:3d4b, 00ca 00d2 0001

192.168.193.200 27/10 16:13:45.234

<151>[5060]STUN trying 0

192.168.193.200 27/10 16:14:15.062

<151>[8008]STUN trying 0

192.168.193.200 27/10 16:14:15.062

<151>[8009]STUN trying 0

192.168.193.200 27/10 16:14:15.062

<151>[8010]STUN trying 0

192.168.193.200 27/10 16:14:15.062

<151>[8011]STUN trying 0

192.168.193.200 27/10 16:14:15.062

<151>[0:0]CC:STUN OK:c0a8c1c8->4d6ad70a, 5060->5060 8008->8008

192.168.193.200 27/10 16:14:15.109

<151>[0:0]AUD ALLOC CALL (port=8008)

192.168.193.200 27/10 16:14:15.109

<151>[0:0]RTP Rx Up

192.168.193.200 27/10 16:14:15.109

<159>[0]Off Hook

192.168.193.200 27/10 16:14:19.797

<151>CC:Connected

192.168.193.200 27/10 16:14:19.875

<151>[0:0]ENC INIT 8

192.168.193.200 27/10 16:14:19.875

<151>[0:0]RTP Tx Up (pt=8->c0a8c064:8000)

192.168.193.200 27/10 16:14:19.875

<151>[0:0]RTCP Tx Up

192.168.193.200 27/10 16:14:19.890

<151>[0:0]RTP Rx 1st PKT @8008(5)

192.168.193.200 27/10 16:14:20.000

<151>[0:0]DEC INIT 8

192.168.193.200 27/10 16:14:20.109

<151>[0]AUD:FAX Event=2

192.168.193.200 27/10 16:14:23.672

<151>[0:0]ENC INIT 8

192.168.193.200 27/10 16:14:23.672

<151>DLG:ReAllocCodecList

192.168.193.200 27/10 16:14:27.453

<159>[0]On Hook

192.168.193.200 27/10 16:15:09.172

<159>[0]FM Alert Stop RxTx (c=00241694;a=0)

192.168.193.200 27/10 16:15:09.187

<151>[0:0]AUD Rel Call

192.168.193.200 27/10 16:15:09.187

<151>DLG Terminated 294eb0

192.168.193.200 27/10 16:15:09.203

<151>Sess Terminated

192.168.193.200 27/10 16:15:09.203

<151>CC:Clean Up

192.168.193.200 27/10 16:15:42.172

<151>— OBJ POOL STAT —

192.168.193.200 27/10 16:15:42.187

<151>OP:RTPRXB = 96 ( 96 192) 192.168.193.200 27/10 16:15:42.187

<151>OP:RTPREB = 40 ( 40 48)

192.168.193.200 27/10 16:15:42.187

<151>OP:RTPTXB = 64 ( 64 108) 192.168.193.200 27/10 16:15:42.187

<151>OP:TIMEOU = 111 (120 52)

192.168.193.200 27/10 16:15:42.187

<151>OP:SIPCOR = 0 ( 1 28) 192.168.193.200 27/10 16:15:42.187

<151>OP:SIPCTS = 32 ( 32 1140)

192.168.193.200 27/10 16:15:42.187

<151>OP:SIPSTS = 32 ( 32 6620) 192.168.193.200 27/10 16:15:42.187

<151>OP:SIPAUS = 0 ( 8 588)

192.168.193.200 27/10 16:15:42.187

<151>OP:SIPDLG = 10 ( 10 148) 192.168.193.200 27/10 16:15:42.187

<151>OP:SIPSES = 12 ( 12 9776)

192.168.193.200 27/10 16:15:42.187

<151>OP:SIPREG = 3 ( 4 304) 192.168.193.200 27/10 16:15:42.187

<151>OP:SIPLIN = 0 ( 2 140)

192.168.193.200 27/10 16:15:42.187

<151>OP:SUBDLG = 2 ( 2 6436) 192.168.193.200 27/10 16:15:42.187

<151>OP:STUNTS = 16 ( 16 68)

192.168.193.200 27/10 16:15:42.187

<151>OP:XMNODE = 1024 (1024 112) 192.168.193.200 27/10 16:15:42.187

<151>

192.168.193.200 27/10 16:15:42.187

<159>fu:1:3d82, 00d4 0160 0161 0162 017a 0001

192.168.193.200 27/10 16:16:20.515

<159>system request reboot

192.168.193.200 27/10 16:16:20.562

<159>fu:1:3d9f, 0038 0445 0001

192.168.193.200 27/10 16:16:20.594

<159>fu:1:3df8, 03e4 05b0 0001

192.168.193.200 27/10 16:16:20.640

<134>System started: ip@192.168.193.200, reboot reason:W4

192.168.193.200 27/10 16:16:25.094

<134>System started: ip@192.168.193.200, reboot reason:W4

192.168.193.200 27/10 16:16:25.094

<143> subnet mask: 255.255.255.0

192.168.193.200 27/10 16:16:25.094

<143> gateway ip: 192.168.193.1

192.168.193.200 27/10 16:16:25.094

<143> dns servers(1): 192.168.193.200 27/10 16:16:25.094

<143>192.168.192.100 192.168.193.200 27/10 16:16:25.094

<143>

192.168.193.200 27/10 16:16:25.094

<159>IDBG: st-0

192.168.193.200 27/10 16:16:33.390

<134>YM:ERR:AuthServerNotConfig

192.168.193.200 27/10 16:16:33.406

<134>YM:ERR:AuthServerNotConfig

192.168.193.200 27/10 16:16:33.406

<134>YM:ERR:AuthServerNotConfig

192.168.193.200 27/10 16:16:33.406

<134>YM:ERR:AuthServerNotConfig

192.168.193.200 27/10 16:16:33.422

<151>[5060]STUN trying 0

192.168.193.200 27/10 16:16:33.422

<151>[0]REG: STUN c0a8c1c8->4d6ad70a, 5060->5060

192.168.193.200 27/10 16:16:33.437

<134>[0]Reg Addr Change(0) 0:0->c0a8c064:5060

192.168.193.200 27/10 16:16:33.437

<134>[0]Reg Addr Change(0) 0:0->c0a8c064:5060

192.168.193.200 27/10 16:16:33.453

<151>[5060]STUN trying 0

192.168.193.200 27/10 16:16:33.453

<151>[0]REG: STUN c0a8c1c8->4d6ad70a, 5060->5060

192.168.193.200 27/10 16:16:33.469

<159>[0]RegOK. NextReg in 3570 (1)

192.168.193.200 27/10 16:16:33.484

<159>fs:12081:12156:65536

192.168.193.200 27/10 16:16:33.625

<159>fls:af:1:0:0

192.168.193.200 27/10 16:16:33.625

<159>fbr:1:3000:3000:13df8:000a:000b:5.2.5

192.168.193.200 27/10 16:16:33.640

<159>fhs:01:0:0001:upg:app:0:3.3.6

192.168.193.200 27/10 16:16:33.640

<159>fhs:02:0:0002:upg:app:1:3.3.6

192.168.193.200 27/10 16:16:33.656

<159>fhs:03:0:0003:upg:app:2:3.3.6

192.168.193.200 27/10 16:16:33.656

<159>fhs:04:0:0004:upg:app:0:5.1.12

192.168.193.200 27/10 16:16:33.687

<159>fhs:05:0:0005:upg:app:0:5.1.12

192.168.193.200 27/10 16:16:33.703

<159>fhs:06:0:0006:upg:app:1:5.1.12

192.168.193.200 27/10 16:16:33.734

<159>fhs:07:0:0007:upg:app:2:5.1.12

192.168.193.200 27/10 16:16:33.750

<159>fhs:08:0:0008:upg:app:0:5.2.3

192.168.193.200 27/10 16:16:33.781

<159>fhs:09:0:0009:upg:app:1:5.2.3

192.168.193.200 27/10 16:16:33.797

<159>fhs:0a:0:000a:upg:app:2:5.2.3

192.168.193.200 27/10 16:16:33.812

<159>fhs:0b:0:000b:upg:app:0:5.2.5

192.168.193.200 27/10 16:16:33.844

<159>fhs:0c:0:000c:upg:app:1:5.2.5

192.168.193.200 27/10 16:16:33.859

<159>fhs:0d:0:000d:upg:app:2:5.2.5

192.168.193.200 27/10 16:16:33.890

<159>fu:1:3e1f, 0003 0001

192.168.193.200 27/10 16:16:34.031

<151>[5060]STUN trying 0

192.168.193.200 27/10 16:17:08.812

<151>[8004]STUN trying 0

192.168.193.200 27/10 16:17:08.812

<151>[8005]STUN trying 0

192.168.193.200 27/10 16:17:08.812

<151>[8006]STUN trying 0

192.168.193.200 27/10 16:17:08.812

<151>[8007]STUN trying 0

192.168.193.200 27/10 16:17:08.812

<151>[0:0]CC:STUN OK:c0a8c1c8->4d6ad70a, 5060->5060 8004->8004

192.168.193.200 27/10 16:17:08.859

<151>[0:0]AUD ALLOC CALL (port=8004)

192.168.193.200 27/10 16:17:08.875

<151>[0:0]RTP Rx Up

192.168.193.200 27/10 16:17:08.890

<159>[0]Off Hook

192.168.193.200 27/10 16:17:12.797

<151>CC:Connected

192.168.193.200 27/10 16:17:12.875

<151>[0:0]ENC INIT 8

192.168.193.200 27/10 16:17:12.890

<151>[0:0]RTP Tx Up (pt=8->c0a8c064:8000)

192.168.193.200 27/10 16:17:12.890

<151>[0:0]RTCP Tx Up

192.168.193.200 27/10 16:17:12.906

<151>[0:0]RTP Rx 1st PKT @8004(3)

192.168.193.200 27/10 16:17:12.906

<159>[0:0]RTP RX:Dup Pkt 1

192.168.193.200 27/10 16:17:12.953

<151>RTP:SSRC changed 4eb82bda->4ba72ec5

192.168.193.200 27/10 16:17:12.984

<151>[0:0]DEC INIT 8

192.168.193.200 27/10 16:17:13.015

<151>DLG:ReAllocCodecList

192.168.193.200 27/10 16:17:20.047

<159>[0]On Hook

192.168.193.200 27/10 16:18:01.781

<159>[0]FM Alert Stop RxTx (c=00241694;a=0)

192.168.193.200 27/10 16:18:01.781

<151>[0:0]AUD Rel Call

192.168.193.200 27/10 16:18:01.797

<151>DLG Terminated 294cf4

192.168.193.200 27/10 16:18:01.797

<151>Sess Terminated

192.168.193.200 27/10 16:18:01.812

16:11:57 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Supported: 100rel

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 316

v=0

o=BroadWorks 44861336 1 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=audio 18150 RTP/AVP 18 97 8 0 98 96 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:11:57 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:11:57 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19786008

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 63 INVITE

Max-Forwards: 8

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 305

v=0

o=BroadWorks 44861336 1 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=audio 8000 RTP/AVP 8 0 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:11:57 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 100 Trying

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 63 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19786008;rport=5060

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:11:57 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 180 Ringing

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 63 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19786008;rport=5060

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 0

—————————————————————-

16:11:57 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:11:59 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:01 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:03 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:04 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 63 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19786008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 258

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

Content-Type: application/sdp

v=0

o=- 36500582 36500582 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8004 RTP/AVP 0 100 101

a=rtpmap:0 PCMU/8000

a=rtpmap:100 NSE/8000

a=fmtp:100 192-193

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

—————————————————————-

16:12:04 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK1q8jng1060vg2cofc241.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 INVITE

User-Agent: Virtual PBX 2.01

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY

Accept: application/sdp

Supported: replaces

Content-Type: application/sdp

Content-Length: 308

v=0

o=- 36500582 36500582 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8002 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:100 NSE/8000

a=fmtp:100 192-193

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

a=domain:XXX.XXX.XXX.XXX

a=local:192.168.192.100 8002

—————————————————————-

16:12:04 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718752 ACK

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:12:04 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19796008

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 63 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:12 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381cbvod0lg1.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718753 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Supported:

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 112

v=0

o=BroadWorks 44861336 2 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=image 18150 udptl t38

—————————————————————-

16:12:12 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19806008

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 64 INVITE

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 114

v=0

o=BroadWorks 44861336 2 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=image 18150 udptl t38

—————————————————————-

16:12:12 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 488 Not Acceptable Here

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 64 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19806008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Warning: 304 spa «Media type not available»

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:12:12 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 415 Unsupported Media Type

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381cbvod0lg1.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718753 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:12 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381cbvod0lg1.1

CSeq: 523718753 ACK

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

Call-ID: BW1611568632710082002400232@213.85.168.66

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:12:12 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19806008

To: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 64 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:45 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

REGISTER sip:qwerty.cnt.ru SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bK19816008

Max-Forwards: 20

To: <sip:8499502XXXX@qwerty.cnt.ru>

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1708 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=3600;q=0.90

Authorization: Digest username=»8499502XXXX»,realm=»qwerty.cnt.ru»,nonce=»BroadWorksXfmt3azkmTo7y9m0BW»,uri=»sip:qwerty.cnt.ru»,response=»0c7f4706cb5c538511e2ef82588271c8″,opaque=»»,algorithm=MD5

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:45 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;received=XXX.XXX.XXX.XXX;branch=z9hG4bK19816008;rport=5060

To: <sip:8499502XXXX@qwerty.cnt.ru>;tag=aprq726bvc2-vuljq9200g1oa

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1708 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=120

—————————————————————-

16:12:54 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:101@192.168.192.100:5060 SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-5199cdc1;rport

From: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

Max-Forwards: 70

User-Agent: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:12:54 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-5199cdc1;rport

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5696

From: <sip:101@mx.XX.ru>;tag=125b8f942827bc61i0

Call-ID: 1224935336-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:12:59 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381cdvod05h1.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718754 BYE

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:12:59 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bK64o9lv100gth1eo0o381cdvod05h1.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5697

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=398336423-1225113116863-

Call-ID: BW1611568632710082002400232@213.85.168.66

CSeq: 523718754 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:15 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Supported: 100rel

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 316

v=0

o=BroadWorks 44862763 1 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=audio 30278 RTP/AVP 18 97 8 0 98 96 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:14:15 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:15 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19826008

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 813 INVITE

Max-Forwards: 8

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 305

v=0

o=BroadWorks 44862763 1 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=audio 8000 RTP/AVP 8 0 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:14:15 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 100 Trying

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 813 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19826008;rport=5060

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:14:15 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 180 Ringing

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 813 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19826008;rport=5060

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 0

—————————————————————-

16:14:15 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:17 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:19 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:19 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 813 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19826008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 258

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

Content-Type: application/sdp

v=0

o=- 36514349 36514349 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8008 RTP/AVP 8 100 101

a=rtpmap:8 PCMA/8000

a=rtpmap:100 NSE/8000

a=fmtp:100 192-193

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

—————————————————————-

16:14:19 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKoh6ric102oah9e892341.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 INVITE

User-Agent: Virtual PBX 2.01

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY

Accept: application/sdp

Supported: replaces

Content-Type: application/sdp

Content-Length: 308

v=0

o=- 36514349 36514349 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8002 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:100 NSE/8000

a=fmtp:100 192-193

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

a=domain:XXX.XXX.XXX.XXX

a=local:192.168.192.100 8002

—————————————————————-

16:14:19 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787628 ACK

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:14:19 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19836008

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 813 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:27 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0cbv0eqlm1.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787629 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Supported:

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 112

v=0

o=BroadWorks 44862763 2 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=image 30278 udptl t38

—————————————————————-

16:14:27 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19846008

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 814 INVITE

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 114

v=0

o=BroadWorks 44862763 2 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=image 30278 udptl t38

—————————————————————-

16:14:27 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 488 Not Acceptable Here

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 814 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19846008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Warning: 304 spa «Media type not available»

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:14:27 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 415 Unsupported Media Type

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0cbv0eqlm1.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787629 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:27 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0cbv0eqlm1.1

CSeq: 523787629 ACK

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

Call-ID: BW161414614271008-1402235193@213.85.168.66

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:14:27 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19846008

To: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 814 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:35 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

REGISTER sip:qwerty.cnt.ru SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bK19856008

Max-Forwards: 20

To: <sip:8499502XXXX@qwerty.cnt.ru>

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1709 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=3600;q=0.90

Authorization: Digest username=»8499502XXXX»,realm=»qwerty.cnt.ru»,nonce=»BroadWorksXfmt3azkmTo7y9m0BW»,uri=»sip:qwerty.cnt.ru»,response=»0c7f4706cb5c538511e2ef82588271c8″,opaque=»»,algorithm=MD5

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:14:35 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;received=XXX.XXX.XXX.XXX;branch=z9hG4bK19856008;rport=5060

To: <sip:8499502XXXX@qwerty.cnt.ru>;tag=aprq726bvc2-vuljq9200g1qa

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1709 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=120

—————————————————————-

16:15:09 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:101@192.168.192.100:5060 SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-83411f0a;rport

From: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

Max-Forwards: 70

User-Agent: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:15:09 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-83411f0a;rport

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5698

From: <sip:101@mx.XX.ru>;tag=263b00a27f498472i0

Call-ID: 1224935337-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:15:11 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0cdv0eq5n1.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787630 BYE

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:15:11 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKcrul6u100gcgsd45v4c0cdv0eq5n1.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5699

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=993914056-1225113254614-

Call-ID: BW161414614271008-1402235193@213.85.168.66

CSeq: 523787630 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:16:25 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

REGISTER sip:qwerty.cnt.ru SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bK19866008

Max-Forwards: 20

To: <sip:8499502XXXX@qwerty.cnt.ru>

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1710 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=3600;q=0.90

Authorization: Digest username=»8499502XXXX»,realm=»qwerty.cnt.ru»,nonce=»BroadWorksXfmt3azkmTo7y9m0BW»,uri=»sip:qwerty.cnt.ru»,response=»0c7f4706cb5c538511e2ef82588271c8″,opaque=»»,algorithm=MD5

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:16:25 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;received=XXX.XXX.XXX.XXX;branch=z9hG4bK19866008;rport=5060

To: <sip:8499502XXXX@qwerty.cnt.ru>;tag=aprq726bvc2-vuljq9200g1sa

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1710 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=120

—————————————————————-

16:16:33 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

REGISTER sip:192.168.192.100 SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-705a6c42;rport

From: 101 <sip:101@192.168.192.100>;tag=273e608831830d1eo0

To: 101 <sip:101@192.168.192.100>

Call-ID: 1d241e99-c60d7cd8@192.168.193.200

CSeq: 7203 REGISTER

Max-Forwards: 70

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>;expires=3600

User-Agent: Linksys/SPA2102-5.2.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

—————————————————————-

16:16:33 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-705a6c42;rport

To: 101 <sip:101@192.168.192.100>

From: 101 <sip:101@192.168.192.100>;tag=273e608831830d1eo0

Call-ID: 1d241e99-c60d7cd8@192.168.193.200

CSeq: 7203 REGISTER

User-Agent: Virtual PBX 2.01

WWW-Authenticate: Digest realm=»axon@core»,nonce=»v15750qaq51149w»,opaque=»»,stale=FALSE,algorithm=MD5

Content-Length: 0

—————————————————————-

16:16:33 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

REGISTER sip:192.168.192.100 SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-b3162b22;rport

From: 101 <sip:101@192.168.192.100>;tag=273e608831830d1eo0

To: 101 <sip:101@192.168.192.100>

Call-ID: 1d241e99-c60d7cd8@192.168.193.200

CSeq: 7204 REGISTER

Max-Forwards: 70

Authorization: Digest username=»101″,realm=»axon@core»,nonce=»v15750qaq51149w»,uri=»sip:192.168.192.100″,algorithm=MD5,response=»c8f04a23b2a8435c5cde019afa6b7889″,opaque=»»

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>;expires=3600

User-Agent: Linksys/SPA2102-5.2.5

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

—————————————————————-

16:16:33 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-b3162b22;rport

To: 101 <sip:101@192.168.192.100>

From: 101 <sip:101@192.168.192.100>;tag=273e608831830d1eo0

Call-ID: 1d241e99-c60d7cd8@192.168.193.200

CSeq: 7204 REGISTER

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.193.200>;expires=3600;q=0.5

Contact: <sip:101@192.168.193.200>;expires=3600;q=0.5

Content-Length: 0

—————————————————————-

16:17:08 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKevh7ca20e860mb4em0c0.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Supported: 100rel

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 316

v=0

o=BroadWorks 44864789 1 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=audio 27936 RTP/AVP 18 97 8 0 98 96 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:17:08 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKevh7ca20e860mb4em0c0.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:17:08 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19876008

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 563 INVITE

Max-Forwards: 8

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 305

v=0

o=BroadWorks 44864789 1 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=audio 8000 RTP/AVP 8 0 101 13

a=rtpmap:97 G.729b/8000

a=rtpmap:98 G.729a/8000

a=rtpmap:96 G.729ab/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=fmtp:18 annexb=yes

a=ptime:20

a=rtpmap:13 CN/8000

—————————————————————-

16:17:08 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 100 Trying

To: <sip:101@mx.XX.ru>

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 563 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19876008;rport=5060

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:17:08 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 180 Ringing

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 563 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19876008;rport=5060

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 0

—————————————————————-

16:17:08 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKevh7ca20e860mb4em0c0.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:17:10 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKevh7ca20e860mb4em0c0.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:17:12 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 563 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19876008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Server: Linksys/SPA2102-5.2.5

Remote-Party-ID: 101 <sip:101@192.168.192.100>;screen=yes;party=called

Content-Length: 203

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

Content-Type: application/sdp

v=0

o=- 4660 4660 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8004 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

—————————————————————-

16:17:12 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKevh7ca20e860mb4em0c0.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 INVITE

User-Agent: Virtual PBX 2.01

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY

Accept: application/sdp

Supported: replaces

Content-Type: application/sdp

Content-Length: 257

v=0

o=- 4660 4660 IN IP4 XXX.XXX.XXX.XXX

s=-

c=IN IP4 XXX.XXX.XXX.XXX

t=0 0

m=audio 8002 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

a=domain:XXX.XXX.XXX.XXX

a=local:192.168.192.100 8002

—————————————————————-

16:17:12 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874502 ACK

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:17:12 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19886008

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 563 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:17:20 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

INVITE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1cbv8e0r33.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874503 INVITE

Contact: <sip:8499740XXXX@213.85.168.52:5060;transport=udp>

Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE

Supported:

Accept: multipart/mixed,application/media_control+xml,application/sdp

Max-Forwards: 9

Content-Type: application/sdp

Content-Length: 112

v=0

o=BroadWorks 44864789 2 IN IP4 213.85.168.52

s=-

c=IN IP4 213.85.168.52

t=0 0

m=image 27936 udptl t38

—————————————————————-

16:17:20 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

INVITE sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19896008

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 564 INVITE

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Contact: <sip:101@192.168.192.100:5060>

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY

Supported: replaces

Content-Type: application/sdp

Content-Length: 114

v=0

o=BroadWorks 44864789 2 IN IP4 213.85.168.52

s=-

c=IN IP4 192.168.192.100

t=0 0

m=image 27936 udptl t38

—————————————————————-

16:17:20 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 488 Not Acceptable Here

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 564 INVITE

Via: SIP/2.0/UDP 192.168.192.100:5060;branch=z9hG4bK19896008;rport=5060

Contact: 101 <sip:101@XXX.XXX.XXX.XXX:5060>

Warning: 304 spa «Media type not available»

Server: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:17:20 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 415 Unsupported Media Type

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1cbv8e0r33.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874503 INVITE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:17:20 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

ACK sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1cbv8e0r33.1

CSeq: 523874503 ACK

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

Call-ID: BW161708363271008-1520194002@213.85.168.66

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:17:20 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

ACK sip:101@192.168.193.200 SIP/2.0

Via: SIP/2.0/UDP 192.168.192.100:5060;rport;branch=z9hG4bK19896008

To: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 564 ACK

Max-Forwards: 20

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:18:01 UDP Packet Received from 192.168.193.200:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:101@192.168.192.100:5060 SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-12290ab;rport

From: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

Max-Forwards: 70

User-Agent: Linksys/SPA2102-5.2.5

Content-Length: 0

—————————————————————-

16:18:01 UDP Packet Sent to 192.168.193.200:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-12290ab;rport

To: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=5700

From: <sip:101@mx.XX.ru>;tag=19029221d4327106i0

Call-ID: 1224935338-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 101 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:18:03 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

BYE sip:8499502XXXX@XXX.XXX.XXX.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1cdv8e0b43.1

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874504 BYE

Max-Forwards: 9

Content-Length: 0

—————————————————————-

16:18:03 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

SIP/2.0 200 OK

Via: SIP/2.0/UDP 213.85.168.52:5060;branch=z9hG4bKr8l4l6300gagfd8g90s1cdv8e0b43.1

To: «XX»<sip:8499502XXXX@qwerty.cnt.ru>;tag=5701

From: <sip:8499740XXXX@213.85.168.66;user=phone>;tag=300427795-1225113428363-

Call-ID: BW161708363271008-1520194002@213.85.168.66

CSeq: 523874504 BYE

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:18:15 UDP Packet Sent to 213.85.168.52:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

REGISTER sip:qwerty.cnt.ru SIP/2.0

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bK19906008

Max-Forwards: 20

To: <sip:8499502XXXX@qwerty.cnt.ru>

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1711 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=3600;q=0.90

Authorization: Digest username=»8499502XXXX»,realm=»qwerty.cnt.ru»,nonce=»BroadWorksXfmt3azkmTo7y9m0BW»,uri=»sip:qwerty.cnt.ru»,response=»0c7f4706cb5c538511e2ef82588271c8″,opaque=»»,algorithm=MD5

User-Agent: Virtual PBX 2.01

Content-Length: 0

—————————————————————-

16:18:15 UDP Packet Received from 213.85.168.52:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;received=XXX.XXX.XXX.XXX;branch=z9hG4bK19906008;rport=5060

To: <sip:8499502XXXX@qwerty.cnt.ru>;tag=aprq726bvc2-vuljq9200g1ua

From: <sip:8499502XXXX@qwerty.cnt.ru>;tag=5671

Call-ID: 1224935319-6008-CORE@XXX.XXX.XXX.XXX

CSeq: 1711 REGISTER

Contact: <sip:8499502XXXX@XXX.XXX.XXX.XXX:5060>;expires=120

—————————————————————-

Источник

Я настраиваю пользователей «100» и «200», я пытаюсь использовать проект sipml5.

Сервер записывает двух пользователей, пользователя «100» на этом онлайн-Linphone.

Пользователь «200» записывает в sipml5, но для выполнения вызова он показывает эту ошибку:

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | acquiring local media`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | acquired local media streams`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | ICE candidate received: candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0`

`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`INVITE sip:100@172.16.1.203 SIP/2.0<br>
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302
Max-Forwards: 70
To: <sip:100@172.16.1.203>
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7760 INVITE
Contact: <sip:040c805k@cam6bslroe6a.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE
Content-Type: application/sdp
Supported: outbound
User-Agent: SIP.js/0.7.2
Content-Length: 1777
`

`v=0
o=- 6908994037829104915 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio
a=msid-semantic: WMS Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
m=audio 56282 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
c=IN IP4 189.35.140.74
a=rtcp:62060 IN IP4 189.35.140.74
a=candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0
a=candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0
a=candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0
a=candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0
a=ice-ufrag:FK6gzTOP0l95UM39
a=ice-pwd:1ehRZElxNwmCq6mQpetD78w+
a=fingerprint:sha-256 2C:93:D5:54:53:96:34:18:DA:A6:3C:1A:59:5A:32:6B:3E:70:79:78:85:AC:AA:26:8F:D6:0B:5E:9C:DB:4A:8C
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10; useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2011742822 cname:/+L6wPj8ErBqYw3L
a=ssrc:2011742822 msid:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N dce80b6d-4fed-4409-af6c-275e470a0d73
a=ssrc:2011742822 mslabel:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
a=ssrc:2011742822 label:dce80b6d-4fed-4409-af6c-275e470a0d73`


`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | received WebSocket text message:`

`SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302;received=172.16.1.209
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
To: <sip:100@172.16.1.203>;tag=as5f539d65
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7760 INVITE
Server: Asterisk PBX 13.6.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="26be674c"
Content-Length: 0`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`ACK sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK7117302
To: <sip:100@172.16.1.203>;tag=as5f539d65
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
Content-Length: 0
CSeq: 7760 ACK`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`INVITE sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152
Max-Forwards: 70
To: <sip:100@172.16.1.203>
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7761 INVITE
Authorization: Digest algorithm=MD5, username="200", realm="asterisk", nonce="26be674c", uri="sip:100@172.16.1.203", response="7c400e75f1605a4893b99438a18b9560"
Contact: <sip:040c805k@cam6bslroe6a.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INFO,NOTIFY,INVITE
Content-Type: application/sdp
Supported: outbound
User-Agent: SIP.js/0.7.2
Content-Length: 1777`

`v=0
o=- 6908994037829104915 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio
a=msid-semantic: WMS Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
m=audio 56282 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
c=IN IP4 189.35.140.74
a=rtcp:62060 IN IP4 189.35.140.74
a=candidate:3879386089 1 udp 2122260223 172.16.1.209 60702 typ host generation 0
a=candidate:3879386089 2 udp 2122260222 172.16.1.209 45410 typ host generation 0
a=candidate:2847491865 1 tcp 1518280447 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:2847491865 2 tcp 1518280446 172.16.1.209 0 typ host tcptype active generation 0
a=candidate:288014909 2 udp 1686052606 189.35.140.74 62060 typ srflx raddr 172.16.1.209 rport 45410 generation 0
a=candidate:288014909 1 udp 1686052607 189.35.140.74 56282 typ srflx raddr 172.16.1.209 rport 60702 generation 0
a=ice-ufrag:FK6gzTOP0l95UM39
a=ice-pwd:1ehRZElxNwmCq6mQpetD78w+
a=fingerprint:sha-256 2C:93:D5:54:53:96:34:18:DA:A6:3C:1A:59:5A:32:6B:3E:70:79:78:85:AC:AA:26:8F:D6:0B:5E:9C:DB:4A:8C
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10; useinbandfec=1
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2011742822 cname:/+L6wPj8ErBqYw3L
a=ssrc:2011742822 msid:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N dce80b6d-4fed-4409-af6c-275e470a0d73
a=ssrc:2011742822 mslabel:Mdtr3XiGc3ZYftGDwxeYDfspP9DqQwSRd17N
a=ssrc:2011742822 label:dce80b6d-4fed-4409-af6c-275e470a0d73`


`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transaction.ict | z9hG4bK7117302 | Timer D expired for INVITE client transaction z9hG4bK7117302
Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | received WebSocket text message:`

`SIP/2.0 488 Not acceptable here
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152;received=172.16.1.209
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
To: <sip:100@172.16.1.203>;tag=as5f539d65
Call-ID: 4pk6rpr5p1mhfts149uk
CSeq: 7761 INVITE
Server: Asterisk PBX 13.6.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0`



`Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transport | sending WebSocket message:`

`ACK sip:100@172.16.1.203 SIP/2.0
Via: SIP/2.0/WS cam6bslroe6a.invalid;branch=z9hG4bK4757152
To: <sip:100@172.16.1.203>;tag=as5f539d65
From: "200" <sip:200@172.16.1.203>;tag=ur4c0oov9u
Call-ID: 4pk6rpr5p1mhfts149uk
Content-Length: 0
CSeq: 7761 ACK`



    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.inviteclientcontext | closing INVITE session 4pk6rpr5p1mhfts149uk9t8l09v01c`

    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.invitecontext.mediahandler | 4pk6rpr5p1mhfts149uk9t8l09v01c | closing PeerConnection`

    `Mon Dec 14 2015 19:18:51 GMT-0200 (BRST) | sip.transaction.ict | z9hG4bK4757152 | Timer D expired for INVITE client transaction z9hG4bK4757152`

2 ответа

Лучший ответ

488 означает отсутствие совместимости с носителями.

Есть несколько причин для приобретения 488: самая распространенная, у вас нет общих кодеков. Сначала убедитесь, что на вашей звездочке поддерживаются и настроены опусы.

С совместимостью webrtc проблема часто связана с использованием:

UDP/TLS/RTP/SAVPF

Вместо того

RTP/SAVPF

То есть: стандарты webrtc / ietf не полностью определены и продолжают действовать.

Вы можете проверить возможный повторяющийся вопрос / ответ здесь: Freeswitch и webRTC: медиа отклонено с помощью 488


4

Community
23 Май 2017 в 10:29

У меня возникает эта проблема, когда я получаю телефонные звонки с использованием SRTP. Телефонные звонки падают на телефон с 488. Я могу без проблем совершать исходящие зашифрованные звонки.


0

sgtcoder
19 Ноя 2019 в 00:29

Источник

Звоните, записывайте разговоры даже там, где не ловит сотовая связь!
Разговаривайте, отправляйте сообщения и записывайте разговоры в любой точке мира. Мобильная связь без мобильного подключения — это eMotion. Только для абонентов МегаФон.

ВЫГОДНО
Не упускай возможность поделиться впечатлениями. В приложении eMotion все входящие звонки бесплатные.
Исходящие звонки по домашнему тарифу независимо от того, в какой точке мира ты находишься.

ГДЕ УГОДНО
Лондон, Рейкьявик, Нью-Йорк, Алматы, Ватикан?
С eMotion ты везде как дома. Чтобы вернуть беззаботность и окружить себя уютом бесперебойной связи, установи приложение.
Просто подключись к Wi-Fi и звони на мобильные и городские номера любой страны. Приложение позволит общаться даже там, где не ловит сеть.

КОМУ УГОДНО
Звони всем! Даже если они еще не в теме.
Вызовы смогут принять даже те, у кого другой оператор. А еще ты можешь звонить через приложение на городские номера.

БЫСТРО И ПРОСТО
Больше не нужно создавать новые аккаунты и заполнять бесконечные поля.
Просто установи приложение, чтобы начать общаться.

УСЛУГИ
При входе в приложение подключатся услуга: eMotion Звонки. Не переживай, у тут нет абонентской платы, с тебя ничего не спишут. Эта услуга нужна для корректной работы приложения.

What’s New

28 Dec 2022

Version 4.3.18

— в связи с истечением срока поддержки сервиса, вынуждены убрать возможность писать и получать SMS через приложение

Ratings and Reviews



СМС

СМС было первой главной причиной пользования этим приложением. Что у вас там закончилось? Пожалуйста верните!

Если наблюдается медленное соединение при исходящих или входящих звонках и при относительно хорошем интернет соединении — вероятнее всего это значит, что ваш оператор интернет проксирует ваш траффик sip, уточните у них, почему так происходит 🙂 также советуем вам попробовать разные режимы транспорта в расширенных настройках. Больше информации в приложении: Профиль — Вопросы и ответы.



Постоянный запрос пароля

Пользую сервис ещё с Мультифона. Очень удобно. Но постоянный запрос пароля выносит мозг. Неужели тестировщики так не компетентны?



Ошибка 488

Постоянно вылезает ошибка 488 в мобильной сети. Оператор почему-то не знает, что значит эта ошибка, так как ее нет в справочнике. Товарищи-разработчики, что это значит?

Вероятнее всего Ваш интернет провайдер не поддерживает SIP. Пожалуйста уточните в компании провайдера так ли это. Если на стороне провайдера поддерживается соединение по SIP — пожалуйста обратитесь в нашу службу поддержки.

App Privacy

The developer, MegaLabs CJSC, indicated that the app’s privacy practices may include handling of data as described below. For more information, see the developer’s privacy policy.

Data Used to Track You

The following data may be used to track you across apps and websites owned by other companies:



  • Location

Data Linked to You

The following data may be collected and linked to your identity:



  • Location



  • Identifiers

Data Not Linked to You

The following data may be collected but it is not linked to your identity:



  • Usage Data



  • Diagnostics

Privacy practices may vary based on, for example, the features you use or your age. Learn More

Information

Provider
MegaLabs CJSC

Size
121.9 MB

Category

Social Networking

Compatibility
iPhone
Requires iOS 11.0 or later.
iPad
Requires iPadOS 11.0 or later.
iPod touch
Requires iOS 11.0 or later.
Languages

English, Russian

Age Rating
4+

Copyright
© PJSC MegaFon

Price
Free

  • Developer Website

  • App Support

  • Privacy Policy

  • Developer Website

  • App Support

  • Privacy Policy

You Might Also Like

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Emission garage ошибка двигателя
  • Emicon прецизионные кондиционеры коды ошибок

    • ➤