Read if you plan on using any asterisk 1.4 machine

Discussion in 'General' started by tbooth, Apr 23, 2008.

  1. tbooth

    Joined:
    Feb 24, 2007
    Messages:
    338
    Likes Received:
    0
    I have been working closely with Varphonex on issues with any flavor of asterisk 1.4 with their sip trunks. You can register their sip trunks fine but when the system reboots the trunks will no longer accept incoming call but the Freepbx System Status page will still show the sip trunk as being registered.
    HERE IS THE FIX FROM A VARPHONEX ENGINEER.
    We recreated your issue on a Asterisk server. Following is the communication on the fix.
    I made a change in asterisk's sip_additional.conf configuration and
    the varphonex IVR started working again.
    What I notice is the trunk [varphonex] was after the user context
    [sip.varphonex.com] and changing the order fixed the problem.
    I also notice that it follows alphabetic order writing to the
    asterisk configuration, that means the trunk settings must come
    alphabetically before user context.
    After changing the trunk name from varphonex to avarphonex the GUI
    wrote in the right order to the configuration file and inbound calls
    are working again without need to edit manually the configuration file
    after making any changes in the Freepbx GUI.
    ----------------------------------------------------------------------------------------------------------
    So basically in a nutshell when you name the trunk AVARPHONEX instead of a VARPHONEX it will correct the issue. I have tested over the weekend powering down a system about 20 times and the system still works correctly.
     
  2. nothings_found

    Joined:
    Nov 5, 2007
    Messages:
    72
    Likes Received:
    0
    Re:Read if you plan on using any asterisk 1.4 mach

    Thank you for taking the time to warn any future users who might encounter this issue.

    :)
     

Share This Page