Caller hears silence after a carrier move
The 200 OK is fine. The address in c= is not.
The ladder completes. What do you open next?
- The c= line and whether 10.1.2.3 is reachable
- The To display name
- Max-Forwards
- The Allow header
10.1.2.3 is not a public address. The phone will send RTP there and get nothing back.
Every Webex call dies with 488
The trunk is up. The offer has no codec the answerer will take.
Where does 488 point?
- This endpoint rejected the SDP offer
- DNS failed
- The registrar is down
- Max-Forwards hit zero
488 is about this UA’s media, not about routing.
Teams marks the SBC inactive
OPTIONS never completes. The certificate name and the Contact FQDN disagree.
The admin center says inactive. What must succeed first?
- OPTIONS over TLS with 200 OK, and a Contact FQDN
- A UDP REGISTER to port 5060
- An RTP STUN binding
- A BYE
Direct Routing health is OPTIONS, and an IP in Contact is refused.
International minutes at 02:00
A diagnostic, not a recipe. The source address was never on the trust list.
The CDR export shows 200 calls to premium international destinations from one UDP source. First control to check?
- Whether that source is allowed to place VoIP calls
- The phone’s wallpaper
- RTCP jitter
- The SDP ptime
IOS voice trusted-IP authentication is the documented toll-fraud control.
Calls drop at the same age
Both sides want a refresh. They never agreed the interval.
The second response is
- The peer’s minimum session interval is higher than the offer
- The codec list is empty
- DNS SRV failed
- ICE consent expired
422 and Min-SE are session timers.
CUCM inserts an MTP and audio sounds like a tunnel
The INVITE left without SDP. Something on the trunk demanded an MTP.
This INVITE is
- Delayed offer
- Early offer
- A REGISTER
- An ACK
No SDP in the INVITE means the offer is not here.
483 after a routing loop
Two proxies keep sending the request to each other.
The response is 483 Too Many Hops. The header that ran out is
- Max-Forwards
- Content-Length
- ptime
- SSRC
Each hop decrements Max-Forwards. Zero becomes 483.
Unity plays the wrong greeting
The forwarded-from number never arrived.
The PBX sent Diversion. The SBC’s outbound INVITE has no Diversion and no History-Info. Unity keys the greeting from
- The original called number, which is now missing
- The RTP SSRC
- The branch cookie
- ptime
Diversion is widely used and is not the standards-track history mechanism. History-Info is.