>>Как-нибудь удалось решить проблему???? Та же петрушка и у меня.
>
>Пока что нет. Думаю надо IOS менять. У меня стоит 12.4(7h) (c5350-is-mz.124-7h.bin)
>мне вот это понравилось:
кусок лога
May 5 13:32:14.539: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId F1D3BC35 38AF11DE 85C79A04 162 8CB1B, SetupTime 16:31:59.539 EET Tue May 5 2009, PeerAddress 5401103, PeerSubAddress , DisconnectCause 26 , DisconnectText network out of order (38), ConnectTime 16:32:14.539 EET Tue May 5 2009, DisconnectTime 16:32: 14.539 EET Tue May 5 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, Rece ivePackets 0, ReceiveBytes 0
May 5 13:32:26.867: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId F1D3BC35 38AF11DE 85C79A04 162 8CB1B, SetupTime 16:32:14.537 EET Tue May 5 2009, PeerAddress 5401103, PeerSubAddress , DisconnectCause 2F , DisconnectText no resource (47), ConnectTime 16:32:26.867 EET Tue May 5 2009, DisconnectTime 16:32:26.867 EE T Tue May 5 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePacket s 0, ReceiveBytes 0
May 5 13:32:35.355: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId F1D3BC35 38AF11DE 85C79A04 162 8CB1B, SetupTime 16:32:26.865 EET Tue May 5 2009, PeerAddress 5401103, PeerSubAddress , DisconnectCause 2F , DisconnectText no resource (47), ConnectTime 16:32:35.355 EET Tue May 5 2009, DisconnectTime 16:32:35.355 EE T Tue May 5 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePacket s 0, ReceiveBytes 0
May 5 13:32:35.363: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId F1D3BC35 38AF11DE 85C79A04 162 8CB1B, SetupTime 16:31:59.533 EET Tue May 5 2009, PeerAddress 5402111, PeerSubAddress , DisconnectCause 2F , DisconnectText no resource (47), ConnectTime 16:32:35.363 EET Tue May 5 2009, DisconnectTime 16:32:35.363 EE T Tue May 5 2009, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePacket s 0, ReceiveBytes 0
May 5 13:32:35.363: //1664/F1D3BC3585C7/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x461304A8
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 5402111
Called Number : 5401103
Source IP Address (Sig ): 10.84.243.3
Destn SIP Req Addr:Port : 10.84.10.4:49510
Destn SIP Resp Addr:Port : 10.84.10.4:49510
Destination Name : 10.84.10.4
May 5 13:32:35.363: //1664/F1D3BC3585C7/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream : 1
Negotiated Codec : g711ulaw
Negotiated Codec Bytes : 160
Negotiated Dtmf-relay : 0
Dtmf-relay Payload : 0
Source IP Address (Media): 10.84.243.3
Source IP Port (Media): 16732
Destn IP Address (Media): 10.84.10.4
Destn IP Port (Media): 2100
Orig Destn IP Address:Port (Media): 0.0.0.0:0
May 5 13:32:35.363: //1664/F1D3BC3585C7/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 47
Disconnect Cause (SIP) : 503
May 5 13:32:43.240: %SDP-3-SDP_PTR_ERROR: Received invalid SDP pointer from application. Unable to process. -Traceback= 0x411B933C 0x41F2E24C 0x41046574 0x41012730 0x41013DE4 0x410213A0 0x41075A1C 0x41075CB8 0x421F56D C 0x421F56C0
May 5 13:32:43.348: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId 55EE34 7C57F11D AC0A5B01 A5478 04, SetupTime 16:32:43.134 EET Tue May 5 2009, PeerAddress 5402111, PeerSubAddress , DisconnectCause 2F , Di sconnectText no resource (47), ConnectTime 16:32:43.338 EET Tue May 5 2009, DisconnectTime 16:32:43.338 EET T ue May 5 2009, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0 , ReceiveBytes 0
May 5 13:32:43.348: //1669/0055EE34AC0A/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x4612B850
State of The Call : STATE_DEAD
TCP Sockets Used : NO
Calling Number : 5401103
Called Number : 5402111
Source IP Address (Sig ): 10.84.243.3
Destn SIP Req Addr:Port : 10.84.10.4:49510
Destn SIP Resp Addr:Port : 10.84.10.4:49510
Destination Name : 10.84.10.4
Вот этот кусок:
May 5 13:32:43.240: %SDP-3-SDP_PTR_ERROR: Received invalid SDP pointer from application.
Unable to process.
и цитата с сайта киски:
Error Message
%SDP-3-CONFIG_PTR_ERROR: Received invalid config pointer from application. Unable
to process.
Explanation
The SDP library application has an invalid configuration pointer. Because of this error,
the SDP library is unable to process the request that it received. The configuration of the application
will not be as expected, and SDP parsing errors can result, even for valid SDPs.
Recommended Action
Copy the error message exactly as it appears on the console or in the system
log, contact your Cisco technical support representative, and provide the representative with the
gathered information