FW: Ready To Throw Up My Hands In Defeat

Home » Asterisk Users » FW: Ready To Throw Up My Hands In Defeat
Asterisk Users 1 Comment

You don’t say what happens when you start Asterisk, but I’ll assume your registration with your provider is failing. If you turn on SIP debug from CLI you can watch your registration attempts, and see the exact reason for failure. (eg: unreachable vs credentials). Post that output into the list email if you aren’t sure what to make of it.

The numerous similar stanzas have to do with pjsip. Many of the older examples/guides reference a simpler (deprecated) SIP stack, with slightly different syntax. If you google PJSIP + Asterisk config you’ll send the purpose of all of those stanza’s. PJSIP adds a lot of complexity for the outlier use cases (99% of people don’t need all of PJSIP’s capabilities) – but you have to fill it all in. There are some nice diagrams here (https://wiki.asterisk.org/wiki/display/AST/PJSIP+Configuration+Sections+and+Relationships) which explains it fairly well.

Please reply to the list only (so anyone can jump in and benefit from the discussion too)

—–Original Message—

One thought on - FW: Ready To Throw Up My Hands In Defeat

  • Am Mon, May 22, 2023 at 04:50:49PM +0000 schrieb TTT:

    Some CLI commands are usefull to find out which part of the configration is working.

    *CLI> pjsip list endpoints

    the endpoint should be listed as “Not in use”

    *CLI> pjsip list registrations


    ================================================

    sipgate/sip:sipgate.de sipgate Registered (exp. 51s)

    Here the provider is called sipgate.

    For a first test you may replace this by that line:

    exten => _X.,1,Goto(from-internal,100,1)

    (first test only. That call is not “from-internal”)

    “Goto” can be used to jump to another context, extension and priority.


    Stefan Tichy ( asterisk3 at pi4tel dot de )