Lost all communication on sip trunk

› VitalPBX Community Support › General Discussion › Lost all communication on sip trunk

Up
0
Down
  • Post
    • February 1, 2020 at 6:55 pm
    Up
    0
    Down
    Gary
    Participant

    I can no longer make or receive calls on my sip trunk, the trunk is registered and is username 190881 but for some reason in sip show peers it shows dtmfmode/190881 when it should be 190881/190881 I have deleted trunk and reinstalled but the same peer user name appears.

    so when I place a call I get

    [2020-02-01 13:53:38] WARNING[5860][C-0000000c]: chan_sip.c:6331 create_addr: Purely numeric hostname (190881), and not a peer–rejecting!

     

    0
Viewing 11 replies - 1 through 11 (of 11 total)
  • Replies
    • February 1, 2020 at 7:20 pm
    Up
    0
    Down
    Gary
    Participant

    If i create a second sip trunk for testing in sip show peers it does not add a new peer it just changes the one that was already there, dtmfmode/190881 is in sip show peers when I add a new sip trunk 102205_test it should be added to peers instead sip show peers only shows dtmfmode/102205_Test and dtmfmode/190881 is gone, both trunks show as registered on vitalpbx and at ITSP

    0
    • February 1, 2020 at 8:52 pm
    Up
    0
    Down
    Gary
    Participant

    I can register the same sip trunk on another Vitalpbx and it shows as peer 190881/190881 and work fine, does anyone know why this server shows the peer as dtmfmode/190881 this is auto populated 

     

    0
    • February 1, 2020 at 9:52 pm
    Up
    0
    Down
    Gary
    Participant

    in sip__50-1-trunks.conf

    [dtmfmode] is inserted instead of dtmfmode=rfc2833

     

    0
    • February 1, 2020 at 11:30 pm
    Up
    0
    Down
    Gary
    Participant

    If I manually edit sip__50-1-trunks.conf and remove [dtmfmode] and insert dtmfmode=rfc2833 then systemctl restart asterisk the trunk will work But if I make a change in trunks through the gui it will change the settings and stop working, is there a module that can be reloaded to correct this.

     

    0
    • February 3, 2020 at 3:32 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    I’ve tested this on the latest version of VitalPBX, and I am unable to replicate it. 

    I may suggest you remove the trunk, reinstall the VitalPBX RPM, and create the trunk again.

    yum reinstall vitalpbx -y
    0
    • February 3, 2020 at 9:18 pm
    Up
    0
    Down
    Gary
    Participant

    Thank you for your help, will this effect the licensed addon modules.

    0
    • February 4, 2020 at 2:05 am
    Up
    0
    Down
    Gary
    Participant

    I followed instructions and after recreating trunk it has the same issue, this is in sip__50-1-trunks.conf sanitized.

    [1912345678]
    context=trk-4-in
    description=siptrunk
    [dtmfmode]
    host=XXXX.com
    port=5080
    secret=password
    type=friend
    defaultuser=1912345678
    remotesecret=password
    qualify=yes

    I did see 1 PHP error when vitalpbx was reinstalled.

    Total download size: 9.5 M
    Installed size: 35 M
    Downloading packages:
    vitalpbx-2.4.0-3.x86_64.rpm | 9.5 MB 00:00:00
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
    Installing : vitalpbx-2.4.0-3.x86_64 1/1
    Importing 20190723.1.cdr_trunk.sql…
    PHP Fatal error: Uncaught exception ‘Exception’ with message ‘ERROR 1060 (42S21) at line 2: Duplicate column name ‘trunk’
    ‘ in /usr/share/ombutel/scripts/apply_patches:0
    Stack trace:
    #0 /usr/share/ombutel/scripts/apply_patches(0): patcher::shellcmd()
    #1 /usr/share/ombutel/scripts/apply_patches(0): patcher->shellcmd()
    #2 /usr/share/ombutel/scripts/apply_patches(0): patcher->import_dbscript()
    #3 /usr/share/ombutel/scripts/apply_patches(0): patcher->apply()
    #4 {main}
    thrown in /usr/share/ombutel/scripts/apply_patches on line 0
    Verifying : vitalpbx-2.4.0-3.x86_64 1/1

    Installed:
    vitalpbx.x86_64 0:2.4.0-3

    0
    • February 4, 2020 at 4:16 am
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    That’s why is failing, because the patches are not apply correctly.

    0
    • February 4, 2020 at 1:38 pm
    Up
    0
    Down
    Gary
    Participant

    How can I apply them correctly.

    0
    • February 4, 2020 at 3:02 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    Open the file “20190723.1.cdr_trunk.sql” and comment out the content.

    /*alter table asterisk.cdr
    add column `trunk` int unsigned null default null;*/

    Then, apply patches again

    vitalpbx --build-db
    0
    • February 5, 2020 at 3:05 am
    Up
    0
    Down
    Gary
    Participant

    Thank you, every thing is back to normal.

    0
Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.