inbound trunk not registering

Discussion in 'General' started by patspidy, Jan 26, 2011.

  1. patspidy

    Joined:
    May 13, 2010
    Messages:
    14
    Likes Received:
    0
    I have Elastix 2.0 installed. I have an IAX trunk from the ISP Voipstreet. I have the trunk built and outbound calling works fine. However; inbound calling does not work yet. The ISP has stated that my device is "spamming them" and not registering. I have added the following to iax_general_custom.conf : calltokenoptional = 64.136.174.24/255.255.255.0. 64.136.174.24 is the public IP of the ISP to which I'm trying to register. Here are my settings for the trunk:

    Dial rules
    1+NXXNXXXXXX
    1772+NXXXXXX

    Peer Details
    disallow=all
    allow=ulaw
    host=64.136.174.24
    secret=xxxxxxxxxx
    type=friend
    username=xxxxxxxxxxxxxx

    User Context
    voipstreet_in

    User Details
    disallow=all
    allow=ulaw
    context=from-trunk
    host=64.136.174.24
    insecure=very
    secret=xxxxxxxxxxxxxx
    type=friend
    user=xxxxxxxxxxx
    username=xxxxxxxxxxxxx

    Register String
    register => username:secret@chi-reg.voipstreet.com

    When I turn debugging on and look at my logs, I cant see anything regarding the registration of the trunk.

    Here is an example of the full log that is not familiar to me:

    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'ext-local' tries to include nonexistent context 'ext-local-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'from-did-direct-ivr' tries to include nonexistent context 'from-did-direct-ivr-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'from-trunk-iax2-Voipstreet' tries to include nonexistent context 'from-trunk-iax2-Voipstreet-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'outbound-allroutes' tries to include nonexistent context 'outbound-allroutes-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'outrt-001-9_outside' tries to include nonexistent context 'outrt-001-9_outside-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'app-blackhole' tries to include nonexistent context 'app-blackhole-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'bad-number' tries to include nonexistent context 'bad-number-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-confirm' tries to include nonexistent context 'macro-confirm-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-auto-confirm' tries to include nonexistent context 'macro-auto-confirm-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-auto-blkvm' tries to include nonexistent context 'macro-auto-blkvm-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'sub-pincheck' tries to include nonexistent context 'sub-pincheck-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-dialout-trunk' tries to include nonexistent context 'macro-dialout-trunk-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-dialout-dundi' tries to include nonexistent context 'macro-dialout-dundi-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-user-callerid' tries to include nonexistent context 'macro-user-callerid-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-dialout-enum' tries to include nonexistent context 'macro-dialout-enum-custom'
    [Jan 26 10:31:14] WARNING[3046] pbx.c: Context 'macro-outbound-callerid' tries to include nonexistent context 'macro-outbound-callerid-custom'
     
  2. mm.alpha2k

    Joined:
    Jun 19, 2010
    Messages:
    165
    Likes Received:
    0
    The error to show, it has nothing to do with peer registration.

    In the CLI
    'sip show registry'

    logger.conf
    active

    ;dtmf => dtmf
    ;console => notice,warning,error
    ;console => notice,warning,error,debug
    ;messages => notice,warning,error
    ;full => notice,warning,error,debug,verbose
     
  3. fmvillares

    Joined:
    Sep 8, 2007
    Messages:
    1,785
    Likes Received:
    0
    insecure is also not an option in iax trunks..only applied for sip trunking...also try requirecalltoken=no instead of call token to an ip
     
  4. patspidy

    Joined:
    May 13, 2010
    Messages:
    14
    Likes Received:
    0
    Thanks for the input guys. The problem was a simple one, and i'm a little embarrassed by it. I had simply forgotten to forward the IAX port (4569) through the firewall to the PBX. All of my original programming was correct and it's working like a champ!!!
     

Share This Page