Common SIP Issues


Common SIP (Signaling) Issues



Trunks Won't Register

  • Verify your registration string is correct and has the correct SIP Username and Password as found on your ClearlyIP Trunking Dashboard.
    Example: username:password@1.us-central.clearlyip.com
    • On an asterisk based system you can run:
      asterisk -rx 'pjsip show registrations'
      • You should see a status of Registered
      • If you see Rejected, that could mean you have the wrong credintals or the registration timed out. 
  • Verify your PBX is advertising the correct External IP.
  • If your router has a SIP ALG option, try disabling it.  The vast majority of SIP ALG implementations cause more issues than they fix.
    Note: SIP ALG is the Generic term for SIP Application Layer Gateway.  Several Router manufactures have their open term for this feature; SIP Connection Tracking, SIP Transformations

Inbound calls don't connect at all or get refused

  • If this is the case you should see errors in your PBX's logs
  • Make sure you have the correct IP or FQDN for your Host / Server Address, most PBX's will refuse connections from unknown hosts.
  • Make sure you have an inbound route matching the DID you are calling into. 
    • For ClearlyIP Trunking we will send the 10-Digit DID (NPANXXXXXX) by default

Inbound calls drop immediately or are refused

  • If a call connects but drops within a second or so this could be due to an incompatible signal
    • In your PBX log or Packet Captures you may see a message like "501 Method Not Implemented"
      If this is the Case on a call over ClearlyIP Trunks this could be due to your PBX not supporting "In-call CID Updates", in that case contact support to have that feature turned off for your account.

  • Note: Calls lasting more then 2-3 seconds before dropping are more than likely not going to be SIP issues. 






     RSS of this page