The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  вход/выход  слежка  RSS
"1760 Failed to process media parameters"
Вариант для распечатки  
Пред. тема | След. тема 
Форум Маршрутизаторы CISCO и др. оборудование. (VoIP)
Изначальное сообщение [ Отслеживать ]

"1760 Failed to process media parameters"  +/
Сообщение от MichaelG (ok) on 19-Мрт-15, 11:58 
Добрый день, коллеги!

Имеется маршрутизатор Cisco 1760.
Схема 2 SIP Trunk: CUCM 8.6 ---> 1760 ---> MERA (провайдер)

Идет отбой по Reason: MVTSLocal;cause=13;text="[Common] Failed to process media parameters"
На 1760 2 пира на CUCM и на провадера. NAT-а нет.

Cisco IOS Software, C1700 Software (C1700-ADVIPSERVICESK9-M), Version 12.4(25c), RELEASE

Дебаг:

*Mar  9 13:45:33.519: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:470111@192.168.133.84:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK96b2ce36894
From: <sip:4922470416@192.168.0.6>;tag=6540~c8cd8b8a-a0de-4102-84bf-9656c588ba44-23978685
To: <sip:470111@192.168.133.84>
Date: Tue, 17 Mar 2015 10:59:15 GMT
Call-ID: a55d8900-50810903-4a3-600a8c0@192.168.0.6
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <sip:192.168.0.6:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 2774370560-0000065536-0000000106-0100706496
Session-Expires:  1800
P-Asserted-Identity: <sip:4922470416@192.168.0.6>
Remote-Party-ID: <sip:4922470416@192.168.0.6>;party=calling;screen=yes;privacy=off
Contact: <sip:4922470416@192.168.0.6:5060>
Max-Forwards: 70
Content-Length: 0

*Mar  9 13:45:33.555: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK96b2ce36894
From: <sip:4922470416@192.168.0.6>;tag=6540~c8cd8b8a-a0de-4102-84bf-9656c588ba44-23978685
To: <sip:470111@192.168.133.84>;tag=16BD9B-F74
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: a55d8900-50810903-4a3-600a8c0@192.168.0.6
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 101 INVITE
Allow-Events: telephone-event
Content-Length: 0

*Mar  9 13:45:33.559: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2CB38
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
Supported: 100rel,timer,replaces
Min-SE:  1800
Cisco-Guid: 2774370560-65536-106-100706496
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: <sip:4922470416@192.168.133.84>;party=calling;screen=yes;privacy=off
Timestamp: 1015681533
Contact: <sip:4922470416@192.168.133.84:5060>
Call-Info: <sip:192.168.133.84:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event

*Mar  9 13:45:33.563: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.133.84:5060;branch=z9hG4bK2CB38
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
CSeq: 101 INVITE
Contact: <sip:470111@192.168.133.254:5060>
Server: MERA MVTS3G v.4.4.0-24
Timestamp: 1015681533
Content-Length: 0

*Mar  9 13:45:33.603: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.133.84:5060;branch=z9hG4bK2CB38
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
CSeq: 101 INVITE
Contact: <sip:470111@192.168.133.254:5060>
Content-Type: application/sdp
Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, REFER, REGISTER, UPDATE
Server: MERA MVTS3G v.4.4.0-24
X-mera-expires: 86460
Content-Length:   422

v=0
o=- 1426589955 1426589955 IN IP4 192.168.133.254
s=-
c=IN IP4 192.168.133.254
t=0 0
m=audio 22102 RTP/AVP 18 8 0 101 96 97 98
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:96 G729/8000
a=fmtp:96 annexb=no
a=rtpmap:97 G729/8000
a=fmtp:97 annexb=yes
a=rtpmap:98 G729/8000
a=fmtp:98 annexb=yes
a=sendrecv

*Mar  9 13:45:33.611: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2D850
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

*Mar  9 13:45:33.615: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1015681533
CSeq: 102 BYE
Content-Length: 0

*Mar  9 13:45:33.619: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:4922470416@192.168.133.84:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.133.254:5060;rport;branch=z9hG4bK-1081657254-3826357452-352330168-26242885351
Via: SIP/2.0/UDP 192.168.133.254:5061;rport=5061;branch=z9hG4bK-1081657254-3826357452-352330168-2624288535;received=192.168.133.254
From: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
To: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
CSeq: 102 BYE
Contact: <sip:470111@192.168.133.254:5060>
Max-Forwards: 70
User-Agent: MERA MVTS3G v.4.4.0-24
Reason: MVTSLocal;cause=13;text="[Common] Failed to process media parameters"
Content-Length: 0

*Mar  9 13:45:33.631: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.133.254:5060;rport;branch=z9hG4bK-1081657254-3826357452-352330168-26242885351,SIP/2.0/UDP 192.168.133.254:5061;rport=5061;branch=z9hG4bK-1081657254-3826357452-352330168-2624288535;received=192.168.133.254
From: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
To: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
CSeq: 102 BYE

*Mar  9 13:45:34.112: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1015681534
CSeq: 102 BYE
Content-Length: 0

*Mar  9 13:45:35.113: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1015681535
CSeq: 102 BYE
Content-Length: 0

*Mar  9 13:45:37.113: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1015681537
CSeq: 102 BYE
Content-Length: 0

*Mar  9 13:45:41.115: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:470111@192.168.133.254:5060 SIP/2.0
Via: SIP/2.0/UDP  192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1015681541
CSeq: 102 BYE
Content-Length: 0

*Mar  9 13:45:41.123: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.133.84:5060;branch=z9hG4bK2EFC2
From: <sip:4922470416@192.168.133.84>;tag=16BDAF-8CF
To: <sip:470111@192.168.133.254>;tag=3157376934-3826357452-352330168-2624288535
Call-ID: C336402D-329A11D6-8020F7F2-E163597D@192.168.133.84
CSeq: 102 BYE
Contact: <sip:470111@192.168.133.254:5060>
Server: MERA MVTS3G v.4.4.0-24
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
Content-Length: 0

*Mar  9 13:45:41.127: //42/A55D89000000/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x8440E7B8
State of The Call        : STATE_DEAD
TCP Sockets Used         : NO
Calling Number           : 4922470416
Called Number            : 470111
Source IP Address (Sig  ): 192.168.133.84
Destn SIP Req Addr:Port  : 192.168.133.254:5060
Destn SIP Resp Addr:Port : 192.168.133.254:5060
Destination Name         : 192.168.133.254

*Mar  9 13:45:41.127: //42/A55D89000000/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC)    : 16
Disconnect Cause (SIP)   : 481
R1760#

*Mar  9 13:45:41.135: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK96b2ce36894
From: <sip:4922470416@192.168.0.6>;tag=6540~c8cd8b8a-a0de-4102-84bf-9656c588ba44-23978685
To: <sip:470111@192.168.133.84>;tag=16BD9B-F74
Date: Sat, 09 Mar 2002 13:45:33 GMT
Call-ID: a55d8900-50810903-4a3-600a8c0@192.168.0.6
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 101 INVITE
Allow-Events: telephone-event
Content-Length: 0

*Mar  9 13:45:41.139: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:470111@192.168.133.84:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK96b2ce36894
From: <sip:4922470416@192.168.0.6>;tag=6540~c8cd8b8a-a0de-4102-84bf-9656c588ba44-23978685
To: <sip:470111@192.168.133.84>;tag=16BD9B-F74
Date: Tue, 17 Mar 2015 10:59:15 GMT
Call-ID: a55d8900-50810903-4a3-600a8c0@192.168.0.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0

*Mar  9 13:45:41.147: //41/A55D89000000/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x8440C18C
State of The Call        : STATE_DEAD
TCP Sockets Used         : NO
Calling Number           : 4922470416
Called Number            : 470111
Source IP Address (Sig  ): 172.18.101.2
Destn SIP Req Addr:Port  : 192.168.0.6:5060
Destn SIP Resp Addr:Port : 192.168.0.6:5060
Destination Name         : 192.168.0.6

*Mar  9 13:45:41.151: //41/A55D89000000/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream             : 1
Negotiated Codec         : No Codec
Negotiated Codec Bytes   : 0
Negotiated Dtmf-relay    : 0
Dtmf-relay Payload       : 0
Source IP Address (Media): 192.168.133.84
Source IP Port    (Media): 17936
Destn  IP Address (Media): 0.0.0.0
Destn  IP Port    (Media): 0
Orig Destn IP Address:Port (Media): 0.0.0.0:0

*Mar  9 13:45:41.151: //41/A55D89000000/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC)    : 16
Disconnect Cause (SIP)   : 500

Не могу разобраться, с моей стороны косяк или они не докрутили?!

Ответить | Правка | Cообщить модератору

Оглавление

Сообщения по теме [Сортировка по времени | RSS]


1. "1760 Failed to process media parameters"  +/
Сообщение от ShyLion (ok) on 19-Мрт-15, 20:14 
где конфиг диалпиров, кодеков?
Ответить | Правка | ^ к родителю #0 | Наверх | Cообщить модератору

2. "1760 Failed to process media parameters"  +/
Сообщение от MichaelG (ok) on 20-Мрт-15, 06:03 
> где конфиг диалпиров, кодеков?

voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol pass-through g711alaw
h323
sip
!
voice class codec 1
codec preference 1 g711alaw
codec preference 2 g711ulaw
codec preference 3 g729r8
codec preference 4 g729br8
!
dial-peer voice 1 voip
destination-pattern 4922470416        
session protocol sipv2
session target ipv4:192.168.0.6
dtmf-relay h245-alphanumeric rtp-nte
codec g711alaw
fax-relay ecm disable
fax rate disable
no vad
!
dial-peer voice 2 voip
preference 1
destination-pattern ......
session protocol sipv2
session transport udp
session target ipv4:192.168.133.254
voice-class codec 1
dtmf-relay h245-alphanumeric rtp-nte
fax-relay ecm disable
fax rate disable
no vad

На исходящем пире пробовал прописывать принудительно g711a/ulaw - ситуация не меняется.
Пробовал в voice service voip на sip-е биндить интерфейсы, так же не помогает.
Порты все открыты, файрволов нет, nat-ов нет.
Пока добиваюсь исходящих только.

Ответить | Правка | ^ к родителю #1 | Наверх | Cообщить модератору

Архив | Удалить

Рекомендовать для помещения в FAQ | Индекс форумов | Темы | Пред. тема | След. тема




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру