VIDEOCHAT  ::   FAQ  ::   Поиск  ::   Регистрация  ::   Вход

mango-tele.com проблема с исходящими

Проблемы Asterisk без вэб-оболочек и их решения

Модераторы: april22, Zavr2008

svd
Сообщения: 169
Зарегистрирован: 19 июл 2011, 08:13
Откуда: Красноярск
Контактная информация:

mango-tele.com проблема с исходящими

Сообщение svd »

Всем Всем хорошего настроения!

ни разу не заводил транк с мангой. потратил два часа, и в поддержку звонил и понял что чего то не понимаю.

есть учётка вида user1@vpbx1234567890.mangosip.ru
secret=123456

создаю в эластиксе транк:

user=user1
host=vpbx1234567890.mangosip.ru
fromuser=user1
fromdomain=vpbx1234567890.mangosip.ru
secret=123456
type=friend
qualify=300
port=5060
nat=force_rport
insecure=port,invite
dtmfmode=rfc2833
disallow=all
context=from-trunk
canreinvite=no
allow=ulaw&alaw

со строкой регистрации никаких проблем

user1:123456@vpbx1234567890.mangosip.ru/user1

регистрируется, звонки прилетают, полёт нормальный

outbound_CID = user1
тех поддержка их так сказала, хотя я сомневался.

звоню - не звонит. получаю ошибку...

-звоню в тех поддержку,спрашиваю чего не нравится вашему серваку
-отвечают звонка не видно, но в tcpdump видно что мой сервер присылает инвайт (без регистрационных данных), они ему в ответ запрос 401 - авторизуйся, а он в ответ опять инвайт, такой же как и в первый раз.

Внимание вопрос:
какой параметр заставит моего сервера отвечать им на этот вопрос, или инвайт слать сразу с учётными данными? (некоторый пробел в знаниях ощущаю)
ded
Сообщения: 15631
Зарегистрирован: 26 авг 2010, 19:00

Re: mango-tele.com проблема с исходящими

Сообщение ded »

А Вы сделайте на своей стороне
tcpdump host vpbx1234567890.mangosip.ru and port 5060 -s0 -A
и посмотрите, так ли выглядят ивайты как они рассказывают?
svd
Сообщения: 169
Зарегистрирован: 19 июл 2011, 08:13
Откуда: Красноярск
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение svd »

не до конца понимаю этот ответ моего сервера
4 0.079087 89.250.18.70 81.88.86.11 SIP 521 Request: ACK sip:84956297219@vpbx1234567890.mangosip.ru:5060 |
несет ли он то что от него спросила манго
но какой то ответ есть, сейчас попробую узнать что такое sip 521

Код: Выделить всё

No.     Time        Source                Destination           Protocol Length Info
      1 0.000000    89.250.18.70          81.88.86.11           SIP/SDP  927    Request: INVITE sip:84956297219@vpbx1234567890.mangosip.ru:5060 | 

Frame 1: 927 bytes on wire (7416 bits), 927 bytes captured (7416 bits)
Ethernet II, Src: Vmware_99:ba:67 (00:0c:29:99:ba:67), Dst: Cisco_66:2e:4d (00:1e:f6:66:2e:4d)
Internet Protocol Version 4, Src: 89.250.18.70 (89.250.18.70), Dst: 81.88.86.11 (81.88.86.11)
User Datagram Protocol, Src Port: 18636 (18636), Dst Port: sip (5060)
Session Initiation Protocol (INVITE)

No.     Time        Source                Destination           Protocol Length Info
      2 0.071733    81.88.86.11           89.250.18.70          SIP      406    Status: 100 Trying | 

Frame 2: 406 bytes on wire (3248 bits), 406 bytes captured (3248 bits)
Ethernet II, Src: Cisco_66:2e:4d (00:1e:f6:66:2e:4d), Dst: Vmware_99:ba:67 (00:0c:29:99:ba:67)
Internet Protocol Version 4, Src: 81.88.86.11 (81.88.86.11), Dst: 89.250.18.70 (89.250.18.70)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 18636 (18636)
Session Initiation Protocol (100)

No.     Time        Source                Destination           Protocol Length Info
      3 0.072154    81.88.86.11           89.250.18.70          SIP      576    Status: 401 Unauthorized | 

Frame 3: 576 bytes on wire (4608 bits), 576 bytes captured (4608 bits)
Ethernet II, Src: Cisco_66:2e:4d (00:1e:f6:66:2e:4d), Dst: Vmware_99:ba:67 (00:0c:29:99:ba:67)
Internet Protocol Version 4, Src: 81.88.86.11 (81.88.86.11), Dst: 89.250.18.70 (89.250.18.70)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 18636 (18636)
Session Initiation Protocol (401)

No.     Time        Source                Destination           Protocol Length Info
      4 0.079087    89.250.18.70          81.88.86.11           SIP      521    Request: ACK sip:84956297219@vpbx1234567890.mangosip.ru:5060 | 

Frame 4: 521 bytes on wire (4168 bits), 521 bytes captured (4168 bits)
Ethernet II, Src: Vmware_99:ba:67 (00:0c:29:99:ba:67), Dst: Cisco_66:2e:4d (00:1e:f6:66:2e:4d)
Internet Protocol Version 4, Src: 89.250.18.70 (89.250.18.70), Dst: 81.88.86.11 (81.88.86.11)
User Datagram Protocol, Src Port: 18636 (18636), Dst Port: sip (5060)
Session Initiation Protocol (ACK)

No.     Time        Source                Destination           Protocol Length Info
      5 5.026006    81.88.86.11           89.250.18.70          SIP      316    Request: OPTIONS sip:89.250.18.70:18636 | 

Frame 5: 316 bytes on wire (2528 bits), 316 bytes captured (2528 bits)
Ethernet II, Src: Cisco_66:2e:4d (00:1e:f6:66:2e:4d), Dst: Vmware_99:ba:67 (00:0c:29:99:ba:67)
Internet Protocol Version 4, Src: 81.88.86.11 (81.88.86.11), Dst: 89.250.18.70 (89.250.18.70)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 18636 (18636)
Session Initiation Protocol (OPTIONS)

No.     Time        Source                Destination           Protocol Length Info
      6 5.027157    89.250.18.70          81.88.86.11           SIP      511    Status: 200 OK | 

Frame 6: 511 bytes on wire (4088 bits), 511 bytes captured (4088 bits)
Ethernet II, Src: Vmware_99:ba:67 (00:0c:29:99:ba:67), Dst: Cisco_66:2e:4d (00:1e:f6:66:2e:4d)
Internet Protocol Version 4, Src: 89.250.18.70 (89.250.18.70), Dst: 81.88.86.11 (81.88.86.11)
User Datagram Protocol, Src Port: 18636 (18636), Dst Port: sip (5060)
Session Initiation Protocol (200)

второй вариант с tcpdump как советовал ded

Код: Выделить всё

02:44:25.063511 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 274
E.....@.6...QXV............WOPTIONS sip:89.250.18.70:18636 SIP/2.0
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK5412402
From: sip:nat_pinger@mangosip.ru;tag=5e43fd91
To: sip:89.250.18.70:18636
Call-ID: b87a9024-50cbd0e7-60601@81.88.86.11
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0


02:44:25.064259 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 469
E`...)..@.vd....QXV.........SIP/2.0 200 OK
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK5412402;received=81.88.86.11;rport=5060
From: sip:nat_pinger@mangosip.ru;tag=5e43fd91
To: sip:89.250.18.70:18636;tag=as6cbf87db
Call-ID: b87a9024-50cbd0e7-60601@81.88.86.11
CSeq: 1 OPTIONS
Server: XXXIII-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.27.3:5060>
Accept: application/sdp
Content-Length: 0


02:44:26.902449 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 885
E`...*..@.t.....QXV......}..INVITE sip:84956297219@vpbx1234567890.mangosip.ru:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK0654669f;rport
Max-Forwards: 70
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as79a23c87
To: <sip:84956297219@vpbx1234567890.mangosip.ru:5060>
Contact: <sip:user1@192.168.27.3:5060>
Call-ID: 1d37fe8e56d7032b4c3a4afa68661c15@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
User-Agent: XXXIII-PBX
Date: Mon, 30 Mar 2015 18:44:26 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 2021728944 2021728944 IN IP4 192.168.27.3
s=Asterisk PBX 1.8.20.0
c=IN IP4 192.168.27.3
t=0 0
m=audio 11162 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

02:44:26.974973 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 364
E.....@.6..YQXV..........t..SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.27.3:5060;received=89.250.18.70;branch=z9hG4bK0654669f;rport=18636
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as79a23c87
To: <sip:84956297219@vpbx1234567890.mangosip.ru:5060>
Call-ID: 1d37fe8e56d7032b4c3a4afa68661c15@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
Server: Mango SIP
Content-Length: 0


02:44:26.975060 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 534
E..2..@.6...QXV.............SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.27.3:5060;received=89.250.18.70;branch=z9hG4bK0654669f;rport=18636
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as79a23c87
To: <sip:84956297219@vpbx1234567890.mangosip.ru:5060>;tag=e7d2c81e2d36b140069cf4a65dc24be5.8792
Call-ID: 1d37fe8e56d7032b4c3a4afa68661c15@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
WWW-Authenticate: Digest realm="vpbx1234567890.mangosip.ru", nonce="5519999e431517ea261f29c8263d81c0361e48e4", qop="auth"
Server: Mango SIP
Content-Length: 0


02:44:26.975912 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 479
E`...+..@.vX....QXV.........ACK sip:84956297219@vpbx1234567890.mangosip.ru:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK0654669f;rport
Max-Forwards: 70
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as79a23c87
To: <sip:84956297219@vpbx1234567890.mangosip.ru:5060>;tag=e7d2c81e2d36b140069cf4a65dc24be5.8792
Contact: <sip:user1@192.168.27.3:5060>
Call-ID: 1d37fe8e56d7032b4c3a4afa68661c15@vpbx1234567890.mangosip.ru
CSeq: 102 ACK
User-Agent: XXXIII-PBX
Content-Length: 0



12 packets captured
14 packets received by filter
0 packets dropped by kernel
[root@PBX ~]#

svd
Сообщения: 169
Зарегистрирован: 19 июл 2011, 08:13
Откуда: Красноярск
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение svd »

несразумею...
ответил сервер мой им аутентификацией или нет.
пароля нигде не шлётся вроде
ded
Сообщения: 15631
Зарегистрирован: 26 авг 2010, 19:00

Re: mango-tele.com проблема с исходящими

Сообщение ded »

В секции [global] файла sip.conf
поставьте у себя параметры
registertrying=yes
pedantic=yes
Аватара пользователя
Zavr2008
Сообщения: 2215
Зарегистрирован: 27 янв 2011, 00:35
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение Zavr2008 »

-отвечают звонка не видно, но в tcpdump видно что мой сервер присылает инвайт (без регистрационных данных), они ему в ответ запрос 401 - авторизуйся, а он в ответ опять инвайт, такой же как и в первый раз.

Внимание вопрос:
какой параметр заставит моего сервера отвечать им на этот вопрос, или инвайт слать сразу с учётными данными? (некоторый пробел в знаниях ощущаю)
это из-за insecure=port,invite, попробуйте другие значения или вообще уберите..
еще canreinvite устарел, используйте directmedia-no
Российские E1 шлюзы Alvis. Модернизация УПАТС с E1,Подключение к ИС "Антифрод" E1 PRI/SS#7 УВР Телестор, Грифин и др..
svd
Сообщения: 169
Зарегистрирован: 19 июл 2011, 08:13
Откуда: Красноярск
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение svd »

в sip_general_custom поставил
registertrying=yes
pedantic=yes
не помогло

все варианты insecure перепробовал

не помогло

Есть ещё какие то идеи?

дамп звонка с
registertrying=yes
pedantic=yes

Код: Выделить всё

[root@PBX ~]# tcpdump host 81.88.86.11 and port 5060 -s0 -A
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
02:09:12.930354 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 539
E`.7.c..@.
.....QXV......#..OPTIONS sip:vpbx1234567890.mangosip.ru SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK2a5890b3;rport
Max-Forwards: 70
From: "Unknown" <sip:user1@192.168.27.3>;tag=as4791f806
To: <sip:vpbx1234567890.mangosip.ru>
Contact: <sip:user1@192.168.27.3:5060>
Call-ID: 1a75305559c4e26672b24aaa6e86accc@192.168.27.3:5060
CSeq: 102 OPTIONS
User-Agent: XXXIII-PBX
Date: Tue, 31 Mar 2015 18:09:12 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


02:09:12.993367 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 366
E...;&@.6...QXV..........v..SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.27.3:5060;received=89.250.18.70;branch=z9hG4bK2a5890b3;rport=46659
From: "Unknown" <sip:user1@192.168.27.3>;tag=as4791f806
To: <sip:vpbx1234567890.mangosip.ru>;tag=e7d2c81e2d36b140069cf4a65dc24be5.7a6b
Call-ID: 1a75305559c4e26672b24aaa6e86accc@192.168.27.3:5060
CSeq: 102 OPTIONS
Server: Mango SIP
Content-Length: 0


02:09:14.185231 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 271
E..+;'@.6...QXV.............OPTIONS sip:89.250.18.70:46659 SIP/2.0
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK1513563
From: sip:nat_pinger@mangosip.ru;tag=81a6357
To: sip:89.250.18.70:46659
Call-ID: 505ac3f5-45fedf7-3ddf@81.88.86.11
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0


02:09:14.185821 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 466
E`...d..@..,....QXV.......\.SIP/2.0 200 OK
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK1513563;received=81.88.86.11;rport=5060
From: sip:nat_pinger@mangosip.ru;tag=81a6357
To: sip:89.250.18.70:46659;tag=as18b2b5cc
Call-ID: 505ac3f5-45fedf7-3ddf@81.88.86.11
CSeq: 1 OPTIONS
Server: XXXIII-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.27.3:5060>
Accept: application/sdp
Content-Length: 0


02:09:16.355138 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 875
E`...e..@.      .....QXV......s..INVITE sip:84956297219@vpbx1234567890.mangosip.ru SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK3d722cf1;rport
Max-Forwards: 70
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as26ae9920
To: <sip:84956297219@vpbx1234567890.mangosip.ru>
Contact: <sip:user1@192.168.27.3:5060>
Call-ID: 716538595c9386fb5d02895a28077710@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
User-Agent: XXXIII-PBX
Date: Tue, 31 Mar 2015 18:09:16 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 1833218905 1833218905 IN IP4 192.168.27.3
s=Asterisk PBX 1.8.20.0
c=IN IP4 192.168.27.3
t=0 0
m=audio 17508 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

02:09:16.420066 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 359
E...;(@.6..3QXV..........o.=SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.27.3:5060;received=89.250.18.70;branch=z9hG4bK3d722cf1;rport=46659
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as26ae9920
To: <sip:84956297219@vpbx1234567890.mangosip.ru>
Call-ID: 716538595c9386fb5d02895a28077710@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
Server: Mango SIP
Content-Length: 0


02:09:16.420301 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 529
E..-;)@.6...QXV.............SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.27.3:5060;received=89.250.18.70;branch=z9hG4bK3d722cf1;rport=46659
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as26ae9920
To: <sip:84956297219@vpbx1234567890.mangosip.ru>;tag=e7d2c81e2d36b140069cf4a65dc24be5.5ab6
Call-ID: 716538595c9386fb5d02895a28077710@vpbx1234567890.mangosip.ru
CSeq: 102 INVITE
WWW-Authenticate: Digest realm="vpbx1234567890.mangosip.ru", nonce="551ae2e0e439410751d0c9994bfe653be6017cd3", qop="auth"
Server: Mango SIP
Content-Length: 0


02:09:16.420620 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 469
E`...f..@..'....QXV.........ACK sip:84956297219@vpbx1234567890.mangosip.ru SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK3d722cf1;rport
Max-Forwards: 70
From: "user1" <sip:user1@vpbx1234567890.mangosip.ru>;tag=as26ae9920
To: <sip:84956297219@vpbx1234567890.mangosip.ru>;tag=e7d2c81e2d36b140069cf4a65dc24be5.5ab6
Contact: <sip:user1@192.168.27.3:5060>
Call-ID: 716538595c9386fb5d02895a28077710@vpbx1234567890.mangosip.ru
CSeq: 102 ACK
User-Agent: XXXIII-PBX
Content-Length: 0


02:09:24.487300 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 271
E..+;*@.6...QXV...........0HOPTIONS sip:89.250.18.70:46659 SIP/2.0
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK7398478
From: sip:nat_pinger@mangosip.ru;tag=4e28357
To: sip:89.250.18.70:46659
Call-ID: 505ac3f5-0280ef7-dddf@81.88.86.11
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0


02:09:24.488073 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 466
E`...g..@..)....QXV.........SIP/2.0 200 OK
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK7398478;received=81.88.86.11;rport=5060
From: sip:nat_pinger@mangosip.ru;tag=4e28357
To: sip:89.250.18.70:46659;tag=as481137b2
Call-ID: 505ac3f5-0280ef7-dddf@81.88.86.11
CSeq: 1 OPTIONS
Server: XXXIII-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.27.3:5060>
Accept: application/sdp
Content-Length: 0


02:09:34.784880 IP 81.88.86.11.sip > 192.168.27.3.sip: SIP, length: 271
E..+;+@.6...QXV.............OPTIONS sip:89.250.18.70:46659 SIP/2.0
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK9455963
From: sip:nat_pinger@mangosip.ru;tag=d7b9357
To: sip:89.250.18.70:46659
Call-ID: 505ac3f5-9b02ef7-7edf@81.88.86.11
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0


02:09:34.785310 IP 192.168.27.3.sip > 81.88.86.11.sip: SIP, length: 466
E`...h..@..(....QXV.........SIP/2.0 200 OK
Via: SIP/2.0/UDP 81.88.86.11:5060;branch=z9hG4bK9455963;received=81.88.86.11;rport=5060
From: sip:nat_pinger@mangosip.ru;tag=d7b9357
To: sip:89.250.18.70:46659;tag=as32351387
Call-ID: 505ac3f5-9b02ef7-7edf@81.88.86.11
CSeq: 1 OPTIONS
Server: XXXIII-PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:192.168.27.3:5060>
Accept: application/sdp
Content-Length: 0



12 packets captured
12 packets received by filter
0 packets dropped by kernel
svd
Сообщения: 169
Зарегистрирован: 19 июл 2011, 08:13
Откуда: Красноярск
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение svd »

и ещё, с CardTel та же петрушка

sip debug

Код: Выделить всё

PBX*CLI> sip set  debug ip 217.174.178.19
SIP Debugging Enabled for IP: 217.174.178.19
    -- Registered IAX2 '111' (AUTHENTICATED) at 192.168.23.12:1042
  == Using SIP RTP TOS bits 184
  == Using SIP RTP CoS mark 5
    -- Executing [84956297219@from-internal:1] Macro("SIP/115-0000002a", "user-callerid,SKIPTTL,") in new stack
    -- Executing [s@macro-user-callerid:1] Set("SIP/115-0000002a", "AMPUSER=115") in new stack
    -- Executing [s@macro-user-callerid:2] GotoIf("SIP/115-0000002a", "0?report") in new stack
    -- Executing [s@macro-user-callerid:3] ExecIf("SIP/115-0000002a", "1?Set(REALCALLERIDNUM=115)") in new stack
    -- Executing [s@macro-user-callerid:4] Set("SIP/115-0000002a", "AMPUSER=115") in new stack
    -- Executing [s@macro-user-callerid:5] Set("SIP/115-0000002a", "AMPUSERCIDNAME=115") in new stack
    -- Executing [s@macro-user-callerid:6] GotoIf("SIP/115-0000002a", "0?report") in new stack
    -- Executing [s@macro-user-callerid:7] Set("SIP/115-0000002a", "AMPUSERCID=115") in new stack
    -- Executing [s@macro-user-callerid:8] Set("SIP/115-0000002a", "CALLERID(all)="115" <115>") in new stack
    -- Executing [s@macro-user-callerid:9] ExecIf("SIP/115-0000002a", "0?Set(CHANNEL(language)=)") in new stack
    -- Executing [s@macro-user-callerid:10] GotoIf("SIP/115-0000002a", "1?continue") in new stack
    -- Goto (macro-user-callerid,s,19)
    -- Executing [s@macro-user-callerid:19] Set("SIP/115-0000002a", "CALLERID(number)=115") in new stack
    -- Executing [s@macro-user-callerid:20] Set("SIP/115-0000002a", "CALLERID(name)=115") in new stack
    -- Executing [s@macro-user-callerid:21] NoOp("SIP/115-0000002a", "Using CallerID "115" <115>") in new stack
    -- Executing [84956297219@from-internal:2] NoOp("SIP/115-0000002a", "Calling Out Route: moskva") in new stack
    -- Executing [84956297219@from-internal:3] Set("SIP/115-0000002a", "MOHCLASS=default") in new stack
    -- Executing [84956297219@from-internal:4] Set("SIP/115-0000002a", "_NODEST=") in new stack
    -- Executing [84956297219@from-internal:5] Macro("SIP/115-0000002a", "record-enable,115,OUT,") in new stack
    -- Executing [s@macro-record-enable:1] GotoIf("SIP/115-0000002a", "1?check") in new stack
    -- Goto (macro-record-enable,s,4)
    -- Executing [s@macro-record-enable:4] ExecIf("SIP/115-0000002a", "0?MacroExit()") in new stack
    -- Executing [s@macro-record-enable:5] GotoIf("SIP/115-0000002a", "0?Group:OUT") in new stack
    -- Goto (macro-record-enable,s,15)
    -- Executing [s@macro-record-enable:15] GotoIf("SIP/115-0000002a", "0?IN") in new stack
    -- Executing [s@macro-record-enable:16] ExecIf("SIP/115-0000002a", "1?MacroExit()") in new stack
    -- Executing [84956297219@from-internal:6] Macro("SIP/115-0000002a", "dialout-trunk,2,84956297219,") in new stack
    -- Executing [s@macro-dialout-trunk:1] Set("SIP/115-0000002a", "DIAL_TRUNK=2") in new stack
    -- Executing [s@macro-dialout-trunk:2] GosubIf("SIP/115-0000002a", "0?sub-pincheck,s,1") in new stack
    -- Executing [s@macro-dialout-trunk:3] GotoIf("SIP/115-0000002a", "0?disabletrunk,1") in new stack
    -- Executing [s@macro-dialout-trunk:4] Set("SIP/115-0000002a", "DIAL_NUMBER=84956297219") in new stack
    -- Executing [s@macro-dialout-trunk:5] Set("SIP/115-0000002a", "DIAL_TRUNK_OPTIONS=tr") in new stack
    -- Executing [s@macro-dialout-trunk:6] Set("SIP/115-0000002a", "OUTBOUND_GROUP=OUT_2") in new stack
    -- Executing [s@macro-dialout-trunk:7] GotoIf("SIP/115-0000002a", "1?nomax") in new stack
    -- Goto (macro-dialout-trunk,s,9)
    -- Executing [s@macro-dialout-trunk:9] GotoIf("SIP/115-0000002a", "0?skipoutcid") in new stack
    -- Executing [s@macro-dialout-trunk:10] Set("SIP/115-0000002a", "DIAL_TRUNK_OPTIONS=#") in new stack
    -- Executing [s@macro-dialout-trunk:11] Macro("SIP/115-0000002a", "outbound-callerid,2") in new stack
    -- Executing [s@macro-outbound-callerid:1] ExecIf("SIP/115-0000002a", "0?Set(CALLERPRES()=)") in new stack
    -- Executing [s@macro-outbound-callerid:2] ExecIf("SIP/115-0000002a", "0?Set(REALCALLERIDNUM=115)") in new stack
    -- Executing [s@macro-outbound-callerid:3] GotoIf("SIP/115-0000002a", "1?normcid") in new stack
    -- Goto (macro-outbound-callerid,s,6)
    -- Executing [s@macro-outbound-callerid:6] Set("SIP/115-0000002a", "USEROUTCID=") in new stack
    -- Executing [s@macro-outbound-callerid:7] Set("SIP/115-0000002a", "EMERGENCYCID=") in new stack
    -- Executing [s@macro-outbound-callerid:8] Set("SIP/115-0000002a", "TRUNKOUTCID=0000333333001") in new stack
    -- Executing [s@macro-outbound-callerid:9] GotoIf("SIP/115-0000002a", "1?trunkcid") in new stack
    -- Goto (macro-outbound-callerid,s,12)
    -- Executing [s@macro-outbound-callerid:12] ExecIf("SIP/115-0000002a", "1?Set(CALLERID(all)=0000333333001)") in new stack
    -- Executing [s@macro-outbound-callerid:13] ExecIf("SIP/115-0000002a", "0?Set(CALLERID(all)=)") in new stack
    -- Executing [s@macro-outbound-callerid:14] ExecIf("SIP/115-0000002a", "1?Set(CALLERID(all)=0000333333001)") in new stack
    -- Executing [s@macro-outbound-callerid:15] ExecIf("SIP/115-0000002a", "0?Set(CALLERPRES()=prohib_passed_screen)") in new stack
    -- Executing [s@macro-dialout-trunk:12] GosubIf("SIP/115-0000002a", "0?sub-flp-2,s,1") in new stack
    -- Executing [s@macro-dialout-trunk:13] Set("SIP/115-0000002a", "OUTNUM=84956297219") in new stack
    -- Executing [s@macro-dialout-trunk:14] Set("SIP/115-0000002a", "custom=SIP/Moskva_3740888") in new stack
    -- Executing [s@macro-dialout-trunk:15] ExecIf("SIP/115-0000002a", "0?Set(DIAL_TRUNK_OPTIONS=M(setmusic^default)#)") in new stack
    -- Executing [s@macro-dialout-trunk:16] Macro("SIP/115-0000002a", "dialout-trunk-predial-hook,") in new stack
    -- Executing [s@macro-dialout-trunk-predial-hook:1] MacroExit("SIP/115-0000002a", "") in new stack
    -- Executing [s@macro-dialout-trunk:17] GotoIf("SIP/115-0000002a", "0?bypass,1") in new stack
    -- Executing [s@macro-dialout-trunk:18] GotoIf("SIP/115-0000002a", "0?customtrunk") in new stack
    -- Executing [s@macro-dialout-trunk:19] Dial("SIP/115-0000002a", "SIP/Moskva_3740888/84956297219,300,#") in new stack
 == Using SIP RTP TOS bits 184
  == Using SIP RTP CoS mark 5
Audio is at 18662
Adding codec 0x4 (ulaw) to SDP
Adding codec 0x8 (alaw) to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (NAT) to 217.174.178.19:5060:
INVITE sip:84956297219@sip.cardtel.ru:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK051732e8;rport
Max-Forwards: 70
From: "0000333333001" <sip:0000333333001@sip.cardtel.ru>;tag=as169eb965
To: <sip:84956297219@sip.cardtel.ru:5060>
Contact: <sip:0000333333001@192.168.27.3:5060>
Call-ID: 744cfd9712c729a85b9525d3731ace4a@sip.cardtel.ru
CSeq: 102 INVITE
User-Agent: XXXIII-PBX
Date: Tue, 31 Mar 2015 18:35:07 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 261

v=0
o=root 1456333460 1456333460 IN IP4 192.168.27.3
s=Asterisk PBX 1.8.20.0
c=IN IP4 192.168.27.3
t=0 0
m=audio 18662 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

---
    -- Called SIP/Moskva_3740888/84956297219

<--- SIP read from UDP:217.174.178.19:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK051732e8;received=89.250.18.70;rport=3489
From: "0000333333001" <sip:0000333333001@sip.cardtel.ru>;tag=as169eb965
To: <sip:84956297219@sip.cardtel.ru:5060>;tag=as572e5c09
Call-ID: 744cfd9712c729a85b9525d3731ace4a@sip.cardtel.ru
CSeq: 102 INVITE
Server: Rino_SIP
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="sipreg3crdtl", nonce="611d72dc"
Content-Length: 0

<------------->
--- (11 headers 0 lines) ---
Transmitting (NAT) to 217.174.178.19:5060:
ACK sip:84956297219@sip.cardtel.ru:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.27.3:5060;branch=z9hG4bK051732e8;rport
Max-Forwards: 70
From: "0000333333001" <sip:0000333333001@sip.cardtel.ru>;tag=as169eb965
To: <sip:84956297219@sip.cardtel.ru:5060>;tag=as572e5c09
Contact: <sip:0000333333001@192.168.27.3:5060>
Call-ID: 744cfd9712c729a85b9525d3731ace4a@sip.cardtel.ru
CSeq: 102 ACK
User-Agent: XXXIII-PBX
Content-Length: 0


---
    -- SIP/Moskva_3740888-0000002b is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
ded
Сообщения: 15631
Зарегистрирован: 26 авг 2010, 19:00

Re: mango-tele.com проблема с исходящими

Сообщение ded »

Нет, другая. Я бы с таким CALLERID(all)=0000333333001
тоже не выпустил никуда.

Я прошу Вас обращаться в тех поддержку Манго и Cardtel, тут сообща оказывается выполняем за них работу.
Аватара пользователя
Zavr2008
Сообщения: 2215
Зарегистрирован: 27 янв 2011, 00:35
Контактная информация:

Re: mango-tele.com проблема с исходящими

Сообщение Zavr2008 »

From: "Unknown" <sip:user1@192.168.27.3>;tag=as4791f806
веселые у ТС externip и localnet :)

А insecure нужно просто понимать.
Российские E1 шлюзы Alvis. Модернизация УПАТС с E1,Подключение к ИС "Антифрод" E1 PRI/SS#7 УВР Телестор, Грифин и др..
Ответить
© 2008 — 2025 Asterisk.ru
Digium, Asterisk and AsteriskNOW are registered trademarks of Digium, Inc.
Design and development by PostMet-Netzwerk GmbH