मुख्य सामग्री पर जाएँ
तकनीकी 7 नवंबर 2026 9 मिनट का पठन

SIP 488 Not Acceptable Here: कोडेक मिसमैच ठीक करना

A 488 means the two sides share no codec. How SDP offer and answer works, which codecs carriers expect, and how to align G.711, G.729 and Opus on your trunk.

D
7 नवंबर 2026

त्वरित उत्तर

SIP 488 Not Acceptable Here means the far end understood your INVITE but cannot accept the session you described. The usual cause is that the two sides share no audio codec. Compare the codec list in your INVITE with what the carrier accepts, add G.711 (PCMA and PCMU) as a common fallback, then check encryption and packetisation settings.

A call that fails with 488 never rings and never connects, and the dialer log often shows nothing more helpful than "Not Acceptable Here". The good news is that the failure is deterministic: SIP carries a description of the audio you want to send and receive, the far end compares it with what it can do, and a 488 is the answer when they do not overlap. This guide explains the mechanics, shows how to read a trace, and gives a fix order you can follow on any carrier trunk.

What 488 means and where it appears in the call flow

RFC 3261 defines 488 Not Acceptable Here as having the same meaning as 606 (Not Acceptable), but applying only to the specific resource addressed by the Request-URI, so the request may succeed elsewhere. It also allows the response to carry a message body describing the media capabilities of the responder, formatted as SDP when the INVITE did not ask for something else. (RFC 3261, section 21.4.26, checked November 7, 2026.)

That second sentence matters in practice. A well-behaved far end tells you what it would have accepted, and the same RFC defines Warning header codes for this situation, including 305 "Incompatible media format: one or more media formats contained in the session description are not available".

The sequence on an outbound call looks like this:

  1. Your platform sends an INVITE with an SDP body listing the codecs it offers.
  2. The carrier (or the next hop) may answer 100 Trying.
  3. If the carrier cannot use any offered codec, it answers 488 instead of 180 Ringing or 200 OK.
  4. Your platform sends an ACK for the error response, and the call ends before any audio exists.

Because 488 arrives before ringing, a campaign hit by it shows a burst of instant failures rather than unanswered calls. That pattern, instant failure on one destination or one carrier, is the first clue.

SDP offer and answer in plain English

The mechanism behind codec negotiation is the offer/answer model in RFC 3264. One side sends an offer, the other sends an answer, and the answer must stay within the offer. (RFC 3264, checked November 7, 2026.)

  • The offer lists formats in order of preference. On the m=audio line, each number is a format (an RTP payload type) and the first is the one the offerer prefers.
  • The answer picks from the offer. For a stream the answerer accepts, its m= line must include at least one format it can receive, chosen from those in the offer. The answerer is advised to keep the offer's relative order unless it has a reason to change it (section 6.1).
  • The answer has the same number of media lines as the offer. Streams are matched by position (section 6).
  • If there is no common format, the stream is rejected. The standard says the answerer must reject a stream it has no formats in common for by setting the port to zero, and if no formats are in common for any stream, the whole offered session is rejected (section 6.1).
  • Parameters must be repeated. If a format carries a specific fmtp configuration, the answer must repeat the same values for that format.

In a SIP call setup, the rejection can be delivered as a 488 on the INVITE, which is why a 488 is, most often, the visible symptom of "no format in common".

A worked example (illustrative)

The values below are illustrative, not from any real carrier. Your platform offers only G.729 plus the DTMF event format:

m=audio 16400 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000

If the carrier accepts only PCMU (0) and PCMA (8), nothing on the audio line overlaps, because the only audio codec offered is G.729 (payload type 18). The carrier cannot build a valid answer and returns 488. Offering 0 8 18 101 instead gives it two formats it can use, and the call proceeds with the first one both sides share.

Common codecs on carrier trunks

Three codec families account for almost every trunk conversation. The figures below come from the standards cited.

CodecPayload typeRateनोट्स
G.711 PCMU (mu-law)0 (static)8,000 Hz clock, 64 kbit/sUncompressed logarithmic PCM. The common denominator on trunks.
G.711 PCMA (A-law)8 (static)8,000 Hz clock, 64 kbit/sSame codec family, different companding law.
G.72918 (static)8,000 Hz clock, 8 kbit/sCompressed. Lower bandwidth, more processing.
OpusDynamic (96 to 127 range, set in SDP)48,000 Hz clock, 6 to 510 kbit/sWideband capable. Both sides must agree it explicitly.

G.711. ITU-T G.711, "Pulse code modulation (PCM) of voice frequencies", whose edition in force is dated 11/88, is the baseline telephony codec. RFC 3551 gives PCMU payload type 0 and PCMA payload type 8, both with an 8,000 Hz clock, and describes G.711 as a 64 kbit/s PCM channel with 8 bits per sample. (ITU-T G.711 and RFC 3551, checked November 7, 2026.)

G.729. RFC 3551 gives G.729 static payload type 18, an 8,000 Hz RTP clock and an 8 kbit/s rate, with 10 ms frames and a default packet of 20 ms (two frames). It saves bandwidth at the cost of more processing, and some networks do not carry it.

Opus. RFC 6716 defines Opus as a codec for interactive use, scaling from 6 kbit/s narrowband speech to 510 kbit/s, and covering narrowband through fullband. RFC 7587 defines how it rides in RTP: the media type is audio/opus, the RTP clock rate is always 48000, and the payload type is assigned dynamically, so the SDP carries a line such as a=rtpmap:101 opus/48000/2. Because the number is dynamic, the two sides only match on Opus if both announce it. (RFC 6716, RFC 7587, checked November 7, 2026.)

Static versus dynamic is the detail that trips people up. RFC 3551 reserves payload types 96 to 127 for dynamic assignment, and the meaning of such a number applies only to the session that declared it. Never assume that "101" means the same thing on two different networks.

Causes beyond codecs

When the codec lists clearly overlap and you still see 488, check these in order. They are common operational causes, so confirm each against your own trace rather than assuming.

  • Encryption mismatch. One side requires encrypted media (SRTP) while the other offers plain RTP, or the reverse. Check the SRTP setting on both ends. If your platform has a Disabled, Optional, Required choice, Optional is the setting that tolerates either answer; Required fails against a plain-RTP carrier.
  • Packetisation (ptime). RFC 3264 treats the packetisation interval as a receive-side preference that need not match in both directions, but a far end can still refuse a value it cannot handle. Try the common 20 ms.
  • Parameters attached to a format. A format with a specific fmtp line, as Opus often has, must be repeated identically in the answer. A far end that cannot honour the parameters may drop the format.
  • A device rewriting the SDP. A router or firewall feature that inspects and edits SIP, often called SIP ALG, can corrupt or remove codec lines before they reach the carrier. If the INVITE leaving your network differs from the one arriving at the carrier, suspect it and test with the feature disabled.
  • Wrong destination. Because 488 applies to the resource addressed, one carrier route may reject what another accepts. A destination-specific pattern points to that route, not to your platform.

Read a trace: compare the INVITE with the 488

You need a capture from the signalling path, either from your platform's SIP log or a packet capture on the signalling port. Then:

  1. Find the INVITE for a failed call and note its Call-ID.
  2. List the offered formats. Read the numbers on the m=audio line and match each to its a=rtpmap line. Static numbers 0, 8 and 18 may appear without an rtpmap line.
  3. Find the matching 488 by Call-ID. Check for a Warning header (305 means incompatible media format) and for an SDP body describing what the far end would accept.
  4. Compare. If the 488 body lists codecs and none appear in your offer, add one. If the 488 has no body, ask the carrier for their accepted list.
  5. Check a successful call to the same carrier. The codec that appears in its 200 OK answer is proof of something both sides accept.
  6. Compare the INVITE as sent with the INVITE as received if you can capture at the carrier edge. A difference means something in between is editing it.

Fix order

  1. Get the carrier's accepted codec list in writing for every destination you call. Per-destination matters, as the same carrier can use different upstream routes.
  2. Align the preference lists. Put a codec both sides support first. Keep the order consistent with what you want used, because the offerer's first format is its preference.
  3. Add G.711 as a common fallback. Including PCMA and PCMU in every offer gives almost any trunk something to accept. The cost is bandwidth, 64 kbit/s of audio per direction before packet overhead, which is rarely the binding constraint on a trunk with committed capacity.
  4. Remove codecs the carrier cannot use, especially exotic ones with parameters. A short, valid list negotiates more reliably than a long one.
  5. Check encryption and ptime as listed above.
  6. Decide where transcoding happens, if anywhere. If you must connect a G.729-only network to a G.711-only network, someone has to convert. Transcoding can sit in your platform, in your own SBC or at the carrier. It works, but it adds processing and delay, so treat it as a fallback to alignment, not the first fix.
  7. Re-test with one call to each destination, then a small burst, before restarting a campaign.

Codec choice and voice quality

Codec choice sets a ceiling on audio quality before the network adds its own damage. G.711 at 64 kbit/s is the quality reference for narrowband telephony. G.729 at 8 kbit/s trades some fidelity for bandwidth. Opus can run wideband or fullband when both ends support it, but most traffic that touches the public phone network is narrowband at some point, so a wideband codec only pays off end to end where both legs allow it. Whatever you choose, judge it by measured results: the MOS (Mean Opinion Score) glossary entry explains how call quality is scored, and a transcoded call usually scores lower than the same call carried in one codec end to end.

DialerBee कैसे काम करता है

On a DialerBee BYOC gateway, codecs are set on the Codecs tab of the Add Gateway form. Codec Preferences ship in the order PCMA, PCMU, G729, the picker names each codec as a carrier does (for example "G.711 A-law (PCMA)"), and the list can be re-ordered to match your carrier. DTMF Mode defaults to RFC 2833 (telephone-event), with Inband, SIP INFO and Auto-detect available. Transcoding Enabled is off by default and is meant to stay off unless the two sides share no codec. SRTP Mode on the Media tab offers Disabled, Optional and Required. The step-by-step values are in How to connect your SIP trunk (BYOC setup), and the product overview is on the अपना खुद का टेलीकॉम कैरियर लाएँ page. For the commercial side of owning the carrier relationship, see BYOC बनाम bundled telecom, and for definitions, What is a SIP trunk.

सूत्रों का कहना है

  1. RFC 3261, SIP: Session Initiation Protocol, section 21.4.26 (488) and section 20.43 (Warning). rfc-editor.org/rfc/rfc3261 (7 नवंबर 2026 को जाँचा गया)
  2. RFC 3264, An Offer/Answer Model with SDP, sections 5 to 7. rfc-editor.org/rfc/rfc3264 (7 नवंबर 2026 को जाँचा गया)
  3. RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control, payload types and sections 3 and 4.5. rfc-editor.org/rfc/rfc3551 (7 नवंबर 2026 को जाँचा गया)
  4. RFC 6716, Definition of the Opus Audio Codec. rfc-editor.org/rfc/rfc6716 (7 नवंबर 2026 को जाँचा गया)
  5. RFC 7587, RTP Payload Format for the Opus Speech and Audio Codec. rfc-editor.org/rfc/rfc7587 (7 नवंबर 2026 को जाँचा गया)
  6. ITU-T Recommendation G.711, Pulse code modulation (PCM) of voice frequencies, 11/88. itu.int/rec/T-REC-G.711 (7 नवंबर 2026 को जाँचा गया)

अक्सर पूछे जाने वाले प्रश्न

What does SIP 488 Not Acceptable Here mean?

It is a SIP error response meaning the request, usually an INVITE, was understood but its session description cannot be accepted by the resource addressed. In practice it most often means the two sides have no audio codec in common. RFC 3261 says it has the same meaning as 606 but applies only to the specific resource addressed, so the request may succeed elsewhere.

Is a 488 always a codec problem?

No. Codec mismatch is the most common cause, but a 488 can also come from a media-encryption mismatch such as one side requiring SRTP while the other offers plain RTP, from a packetisation (ptime) the far end will not take, or from a device in the path that rewrites the SDP. The Warning header, when present, and the SDP in the trace tell you which.

Which codec is safest to offer to a carrier?

G.711, in its A-law (PCMA) and mu-law (PCMU) forms, is the usual common denominator for carrier trunks. Both have static RTP payload types, 8 for PCMA and 0 for PCMU, defined in RFC 3551, and they need no transcoding between most networks. Confirm the carrier's accepted list in writing rather than assuming.

Can I use Opus on a SIP trunk?

Only if the carrier supports it on that trunk. Opus is defined in RFC 6716 and its RTP payload format in RFC 7587, and it uses a dynamic payload type announced in the SDP, so both sides must agree it explicitly. Many carrier trunks accept only G.711 and sometimes G.729, so keep G.711 in the list as a fallback.

What is the difference between transcoding and codec negotiation?

Negotiation is the two sides agreeing on one codec from lists they both support. Transcoding is a device in the middle converting audio from one codec to another when the two sides cannot agree. Transcoding fixes a mismatch but adds processing and can lower quality, so aligning codec lists is normally the better first fix.

How do I confirm a codec mismatch in a trace?

Capture the INVITE and the 488. In the INVITE, read the format numbers on the m=audio line and the a=rtpmap lines. In the 488, look for a Warning header and any SDP body describing what the far end accepts. If the two lists share no codec, that is the mismatch.

संबंधित पठन

DialerBee को काम करते हुए देखने के लिए तैयार हैं?

15 मिनट के लाइव डेमो का अनुरोध करें, या 14 दिन का फ़्री ट्रायल शुरू करें — न स्लाइड, न कोई प्रतिबद्धता। कॉलिंग तब शुरू होती है जब आपका अपना SIP ट्रंक या PBX जुड़ जाए और मंज़ूर हो जाए।

14 दिन का फ़्री ट्रायल · मुफ़्त AI क्रेडिट · कोई कार्ड नहीं · 11 भाषाएँ · BYOC · अनुपालन में सहायक नियंत्रण

पूरी साइट अंग्रेज़ी में देखें →