Call is disconnected with SIP error 488 - Page 2

Sebastien Denoncin · ‎12-15-2020

Hello the Community

I am currently experiencing a call disconnection problem between Jabber.

Call flow:

Caller Jabber --> CUCM --> UCCX --> CTI Port --> My Agent Jabber

When I check the SIP tarces, I found that we receive an SIP Message 488 Not Acceptable Media.

I think that it's a codec issue or something like that.

How can I confirm the root cause and How can I solve it?

Thanks for your help

Regards

Sébastien

Sebastien Denoncin · ‎01-05-2021

Hello BalajiSivaraj49175

I already checked this step. All G711 are in the top of my list and G722 are in the bottom of my list.

But In the Invite, I can see the G722. I don't know why.

Thanks

BalajiSivaraj49175 · ‎12-24-2020

SIP/2.0 488 Not Acceptable Media
Via: SIP/2.0/TCP 10.99.206.223:60602;branch=z9hG4bK00002704
From: "Maude MIRTO" <sip:202505@ip>;tag=0205857feb8000370000296f-000021d7
To: <sip:6333@ip>;tag=27932613~b9ff6d1f-c80b-4887-8318-8f6b207ea5ac-42132316
Date: Tue, 15 Dec 2020 09:28:35 GMT
Call-ID: 0205857f-eb800007-000076d0-00002876@10.99.206.223
CSeq: 103 INVITE
Allow-Events: presence
Server: Cisco-CUCM11.5
Remote-Party-ID: "Maxime PAULIGNAN" <sip:975202451@ip>;party=called;screen=yes;privacy=off
Contact: <sip:6333@ip:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="CSFBI14Y";video;bfcp
Content-Length: 0

39021291.004 |10:28:35.047 |AppInfo |EnvProcessCdr::outputCdrData CDR data (size-714)- 1,1,605892,42132316,1608024512,2,0,-540122358,"202505","BI194",0,47,4,-540122358,17348,40,20,0,0,0,0,0,0,"0","0",42132577,2,0,1942971146,"975202451","975202451","BI14Y",0,47,4,1942971146,17858,40,20,0,0,0,0,0,0,"0","0",1608024512,1608024515,"920114","878d306b-e116-46df-9005-47d9b0681454","p_iwe_global_internal","p_iwe_global_internal","p_iwe_global_internal","p_iwe_global_ccx",3,"CSFBI194","CSFBI14Y",13,13,0,10,0,4,0,"UCCluster",10,"","",0,"",3,3,0,0,64,64,"","","","10.99.206.223","10.99.207.115",103,3936,10,-540122358,32282,0,103,3936,10,1942971146,26036,0,0,"",3,"0000000000093EC40282E46100000000",0,0,0,"","",2,"","","","","","","","",0,0,"","","","","","","","",0,0,0,"975202451","975202451","920114",""

39021307.000 |10:28:35.047 |SdlSig |SIPDisconnReq |wait |SIPHandler(2,100,82,1) |SIPCdpc(2,100,85,635444) |2,100,14,339388.216^10.99.206.223^* |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] CcbId= 27932613 --TransType=1 --TransSecurity=0 PeerAddr = 10.99.206.223:60602 ccCause= 47 sip_disc_cause= 0
39021307.001 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 3 (SIP_APPLICATION_MSG), for event 8 (SIPSPI_EV_CC_CALL_DISCONNECT)
39021307.002 |10:28:35.047 |AppInfo |//SIP/Stack/States/0x0xd6209998/sipSPIChangeState: 0xd6209998 : State change from (STATE_MIDCALL_LOCAL_RESP_PENDING, SUBSTATE_NONE) to (STATE_ACTIVE, SUBSTATE_NONE)
39021307.003 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sipSPIStopHoldTimer: Stopping hold timer
39021307.004 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sipSPIPushOrigRequestContainerIntoHolde: Request Container Holder is above threshold...tri
39021307.005 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sipSPIStopHoldTimer: Stopping hold timer
39021307.006 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sipSPIAddViaParams: inserted z9hG4bK6b5aa43c5798c7 into via branch list
39021307.007 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sipSPISendBye: Associated container=0xd5950fc0 to Bye
39021307.008 |10:28:35.047 |AppInfo |//SIP/Stack/Transport/0x0xd6209998/sipSPISendBye: Sending BYE to the transport layer
39021307.009 |10:28:35.047 |AppInfo |//SIP/Stack/Transport/0x0xd6209998/sipSPITransportSendMessage: msg=0xde1c4360, addr=10.99.206.223, port=60602, sentBy_port=0, is_req=1, tran
39021307.010 |10:28:35.047 |AppInfo |//SIP/Stack/Transport/0x0/sipInstanceGetConnectionId: gcb=0xd6209998 is already on connection=0xd6580e10 context_list
39021307.011 |10:28:35.047 |AppInfo |//SIP/Stack/Transport/0x0xd6209998/sipTransportLogicSendMsg: Set to send the msg=0xde1c4360
39021307.012 |10:28:35.047 |AppInfo |//SIP/Stack/Transport/0x0xd6209998/sipTransportPostSendMessage: Posting send for msg=0xde1c4360, addr=10.99.206.223, port=60602, connId=84391 for
39021307.013 |10:28:35.047 |AppInfo |//SIP/Stack/Info/0x0xd6209998/sentByeDisconnecting: Sent Bye Request, starting DisconnectTimer
39021307.014 |10:28:35.047 |AppInfo |//SIP/Stack/States/0x0xd6209998/sipSPIChangeState: 0xd6209998 : State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE)
39021307.015 |10:28:35.047 |AppInfo |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: timerContext=0xd620a978 type=SIP_TIMER_DISCONNECT value=500 retries=10
39021307.016 |10:28:35.047 |AppInfo |//SIP/SIPHandler/ccbId=0/scbId=0/sip_start_timer: timerContext=0xd620a978 type=SIP_TIMER_DISCONNECT value=500 retries=10
39021308.000 |10:28:35.048 |SdlSig |DChangeNotifyReq |restart0 |SIPBuiltInBridgeControl(2,100,86,42530) |SIPStationD(2,100,76,68029) |2,100,14,339388.216^10.99.206.223^* |[R:N-H:0,N:3,L:0,V:0,Z:0,D:0] CallPhase=CALL_CLEARING StationEvent=0 CI=42132577 EventQualifier=0
39021308.001 |10:28:35.048 |AppInfo |SIPBuiltInBridgeControl - getBibPrimaryCallData_byRefCI: no primary call with refCI=42132577
39021308.002 |10:28:35.048 |AppInfo |SIPBuiltInBridgeControl - getBibSessionCallData: no session with CI=42132577
39021308.003 |10:28:35.048 |AppInfo |SIPBuiltInBridgeControl::star_DChangeNotifyReq no call record for CI=42132577

Error SIP message

Sebastien Denoncin · ‎01-05-2021

Hi BalajiSivaraj49175

Yes it's the SIP error message but I don't understand why we receive it.

Thanks

Regards

Sébastien

Roger Kallberg · ‎01-05-2021

You need to check why you don’t get a successful codec negotiation. The error indicates that there is either no codec agreed or a needed media resource is not able to be allocated for the call to succeed.

Sebastien Denoncin · ‎01-06-2021

Hello Roger,

I agree with you.

But I don't understand why the codec G722 and G722.1 are in the codec negociation. Because normally, G722 is disable on the CUCM Cluster and in the SIP profil, Cisco gave me a script to remove the G722.1 for another problem.

S normally both codec does not be used in the SIP invite with SDP. Right?

Thanks

regards

Sébastien

Roger Kallberg · ‎01-06-2021

If G722 is disabled or not depends on how you have set a service parameter and an enterprise parameter.

Sebastien Denoncin · ‎02-22-2021

Hello Roger,

G722 is disabled in service parameters and in the enterprise parameter.

I opened a TAC Case because I don't understand the behavior.