How to fix Error SIP 488 Not Acceptable in Cisco Call Manager

January 12th, 2019
Print Friendly, PDF & Email


Unified Communication Clinic #1 (1)

Did you get this SIP error on your Cisco call manager?

You already change all the codec, configured transcoder which is register with call manager and everything seems fine. But outgoing calls still give this error!!!

SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/UDP 192.168.1.1:5060;received=192.168.1.1;branch=fg5df4bK4F1C77
To: <sip:0834738834@88.XXX.XX.XXX>;tag=5435345-43543
From: <sip:0974376437@192.168.1.1>;tag=E435A43-A43
Call-ID: FDF74C45-3C7351E2-64E3FEC8-F5473FD6@192.168.1.1
CSeq: 101 INVITE
Allow: CANCEL, ACK, INVITE, BYE, OPTIONS, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:0834738834@88.XXX.XX.XXX:5060>
Reason: Q.850;cause=65
Content-Length: 0

Based on the Wikipedia article List of SIP response codes

488 Not Acceptable Here
Some aspect of the session description or the Request-URI is not acceptable, or Codec issue.

If we want to go to more deep, the IETF rfc3261 explain about that message:

488 Not Acceptable Here

The response has the same meaning as 606 (Not Acceptable), but only
applies to the specific resource addressed by the Request-URI and the
request may succeed elsewhere.

A message body containing a description of media capabilities MAY be
present in the response, which is formatted according to the Accept
header field in the INVITE (or application/sdp if not present), the
same as a message body in a 200 (OK) response to an OPTIONS request.

Often this is related to codec incompatibilities. For anyone encountering this issue, they should check whether both sides (server and client) have at least one codes they can negotiate.

For fix that you should check both side configuration, I mean if you got an error for a SIP trunk you should check the SIP trunk provider codec and config if it’s interconnection in your company you should check the second server configuration.

For finding and debugging the codec for both side, you can capture SIP session by tools like Wireshark; you can check the codec for each call.

cisco-wireshark-Message-SIP-488-4

To fix it you should go to SIP trunk and look for “MTP Preferred Originating Codec” and change it. Make sure both sides use the same codec.

Step 1:
Login into your Cisco Unified CM Administration and click on Device menu.

cisco-Message-SIP-488-1

Step 2:
Click on Trunk

cisco-Message-SIP-488-2

Step 3:
Select your SIP trunk and click on to change the configuration.

Step 4:
In SIP trunk configuration goto “SIP Information” section and check the value of “MTP Preferred Originating Codec.”

cisco-Message-SIP-488-3

If the problem is still unresolved, there is one more step.
Most of SIP provider want Early Offer INVITEs. They use this always to decide on which codec to offer for the calls.

To configure Delayed-Offer to Early-Offer for SIP Audio Calls at the global level, perform the steps in this section.

Step 1:
Open a terminal and connect to your CUCM console.

Step 2:
And enter the following commands:

1. enable
2. configure terminal
3. voice service voip
4. allow-connections sip
5. early-offer forced
6. exit

Reza Mousavi

Reza Mousavi

Serial Entrepreneur, Founder & CEO at PBXDom, Software Architect, Frequent reader, Fan of adventure travel
Reza Mousavi
Print Friendly, PDF & Email

Share this article on social networks:


Related Posts


Are you ready to start monitoring and analysis your phone systems?

Try PBXDOM for 14 days free
no credit card required.


Try free for 14 days 

Follow us

Follow us and get the latest news through your favorite Social Network