QUESTION Google voice trunks with Obi200 and IncrediblePBX

Discussion in 'Trunks' started by JWTEXAS, May 29, 2018.

  1. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Your obi202 is probably rebooting. Check the uptime on the obi, make test call, check uptime again. You should see it's been running for just a few seconds.
     
  2. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Has anyone determined a cause or solution? Anyone know why reboot isn't occurring on all obi20x systems?
     
  3. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Just installed the same firmware on my OBI200 but I'm still getting reboots with any call. Is this a hardware issue (HardwareVersion 1.4)? How can I make that determination? Really want/need this to work.
     
  4. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    I've setup my obi200 to send syslog data to my laptop. I'm finding the following when it reboots from a call:

    2018-12-01T13:19:57.424104-08:00 192.168.5.32 CCTL:NewCallOn Term 10[0] ->,18436060555
    2018-12-01T13:19:59.644880-08:00 192.168.5.32 RTP: DtmfTxMtd:1(1),0
    2018-12-01T13:19:59.644880-08:00 192.168.5.32 SIP/DLG:Start Early ICE on 18x
    2018-12-01T13:19:59.684394-08:00 192.168.5.32 RTP:Start->4a7d273a:19305(80 0);0;0;0:0:0;0(47)
    2018-12-01T13:19:59.684394-08:00 192.168.5.32 RTP:Set actpass 2
    2018-12-01T13:19:59.694116-08:00 192.168.5.32 DTLS:Setup active
    2018-12-01T13:19:59.965027-08:00 192.168.5.32 DTLS:Handshake Success
    2018-12-01T13:20:00.964739-08:00 192.168.5.32 RTP: PeerRflxAddr=4a7d273a:19305
    2018-12-01T13:20:01.246446-08:00 192.168.5.32 RTP: DtmfTxMtd:1(1),0
    2018-12-01T13:20:01.345251-08:00 192.168.5.32 RTP:Start->c0a8051c:15794(80 0);0;0;0:0:0;0(45)
    2018-12-01T13:20:01.345251-08:00 192.168.5.32 Signal 11 (LR:7cbb8cac PC:d7828) !!!
    2018-12-01T13:20:01.375910-08:00 192.168.5.32 TDM_stop_dma: fd #18
    2018-12-01T13:20:01.375910-08:00 192.168.5.32 TDM_stop_dma: done
    2018-12-01T13:20:01.375910-08:00 192.168.5.32 TDM_stop_dma: fd #19
    2018-12-01T13:20:01.375910-08:00 192.168.5.32 TDM_stop_dma: done

    From what I can find on the internet, this seems to be a bad memory reference? Seems to be a common thread from many sites.
     
  5. David Foxworth

    Joined:
    Oct 26, 2013
    Messages:
    45
    Likes Received:
    14
    obihai_device.png I don't have anything to offer other than what I experienced as documented above. My hardware version is also 1.4, and once I upgraded to the latest 5921EX firmware, the reboot issue stopped. I made no other changes, other than what is documented that you have to change, such as X_InboundCallRoute and X_SpoofCallerID. Also I am using the arrynrob version of firmware, not the stock version from OBiHai....

    Oh and I might add that I have also added another GV number to SP2. In a previous post I was using GV on SP1 and the trunk to my Asterisk server on SP3. I will probably add another GV number to SP4 when time permits...
     
  6. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Very confused by all the hit and miss on the error. Just want to confirm that you have the OBI200, not the OBI202 with router.
     
  7. David Foxworth

    Joined:
    Oct 26, 2013
    Messages:
    45
    Likes Received:
    14
    I have the OBi200...
     
  8. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    I was reasonably sure that was the case, just wanted to verify. I've submitted a request to Polycom/Obi for assistance. I sent them my syslog entries showing the reboot and want to hear what they have to say, if anything.
     
  9. David Foxworth

    Joined:
    Oct 26, 2013
    Messages:
    45
    Likes Received:
    14
    You might try doing a factory reset on your OBi device and trying to reconfigure from scratch. As I mentioned, I had the same issue being reported, but once I got to 5921EX it started working. And I believe after I did the firmware update, I did a factory reset, so perhaps that is the key...
     
  10. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    I've done multiple factory resets with various versions of the firmware, both stock and third-party, to no avail.
     
  11. thatguruguy

    thatguruguy New Member

    Joined:
    Dec 9, 2015
    Messages:
    5
    Likes Received:
    0
    I have the Obi 202, and I have the reboot issue when I use the method described to set up a chan_sip trunk.

    If I try to set up a chan_pjsip trunk instead, I can call out, but I get a "Call ended (403 forbidden) error on my Obi. It would be useful if the tutorial were revised to include instructions on properly setting up the chan_pjsip server.
     
  12. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Someone suggested that there may be an issue with Incredible PBX. Following that suggestion I installed RasPBX on another system and it seems to be working perfectly with the OBI200. I have two Google Voice lines working now. Not sure what the problem is with Incredible PBX but I could never get it to work.
     
  13. TerraHertz

    TerraHertz New Member

    Joined:
    Dec 8, 2018
    Messages:
    4
    Likes Received:
    0
    Alternately you could try the method shown here which does not require the use of pjsip, only thing is that the authors say it was developed on a Raspberry Pi so I can't say whether it will work with IncrediblePBX. But it's an alternative if you don't have pjsip installed, or just prefer to use chan_sip.
     
  14. sortons

    sortons New Member

    Joined:
    Aug 9, 2018
    Messages:
    17
    Likes Received:
    2
    Based on the write-up in the link provided above, the test was on a Raspberry with PBX14 or higher, Asterisk ? (IncrediblePBX is 13/13.) However, the PBX / Asterisk version doesn't seem to be the issue here.
    I have OBis running perfectly fine with FreePBX13 and 14 (with Asterisk 13) installed based on RonR's script here: http://www.dslreports.com/forum/r30661088-PBX-FreePBX-for-the-Raspberry-Pi. The integration I used is based on the instructions linked to post #6.

    That being said it's still overhead to run separate instances for OBi integration and all the rest on IncrediblePBX. Hopefully someone will come up with a good solution on IncrediblePBX (which at this point seems like a hit or miss type scenario.).
     
    #34 sortons, Dec 20, 2018
    Last edited: Dec 20, 2018
  15. bjs.pdx

    bjs.pdx Member

    Joined:
    Oct 6, 2018
    Messages:
    39
    Likes Received:
    0
    Since I couldn't get the OBi to work with IncrediblePBX I switched to RasPBX. Not what I really wanted but I needed the OBi/GoogleVoice integration. If someone finds the issue and a solution, I'd really prefer to move back to IncrediblePBX.
     
  16. sh0tsmash

    sh0tsmash New Member

    Joined:
    Jul 8, 2014
    Messages:
    15
    Likes Received:
    0
    I am having the no audio problem (no audio in either direction). Hardware 1.4; Firmware 3.2.2 (Build: 5921EX). I can also confirm my unit is not rebooting. Calls on a physical handset work just fine.

    Can someone shed some light?

    EDIT: Nothing in the asterisk log files. Interestingly enough, it does not trigger an "Active Call" on the dashboard (it does show in CDR report)
     
    #36 sh0tsmash, Mar 13, 2019 at 9:44 PM
    Last edited: Mar 13, 2019 at 10:02 PM