R.I.P. Google voice trunks with Obi200 and IncrediblePBX

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
I'm in the same boat. Using a obi202 and no audio either way. :-(

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.
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
Has anyone determined a cause or solution? Anyone know why reboot isn't occurring on all obi20x systems?
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
Yes, I would experience that issue with my OBi200 if I modified the X_InboundCallRoute parameter to anything but the phone port. That seemed to be the crucial configuration parameter that would cause the reboots.

Anyway, it now seems to be fixed with the latest firmware, OBi2-3-2-2-5921EX-arrynrob8.fw. It may also be fixed with the stock OBi firmware, however, I have never tried it. But I loaded the arrynrob8 version on my OBi200 and have it configured as a GVSIP bridge to my Asterisk server and I am now able to make and receive calls without the device rebooting.

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.
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
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.
 
Joined
Oct 26, 2013
Messages
69
Reaction score
23
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...
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
View attachment 2221 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...

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.
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
I have the OBi200...

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.
 
Joined
Oct 26, 2013
Messages
69
Reaction score
23
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.

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...
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
0
I've done multiple factory resets with various versions of the firmware, both stock and third-party, to no avail.
 

thatguruguy

New Member
Joined
Dec 9, 2015
Messages
5
Reaction score
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.
 

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
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.
 

TerraHertz

New Member
Joined
Dec 8, 2018
Messages
5
Reaction score
1
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.
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.
 

sortons

Member
Joined
Aug 9, 2018
Messages
60
Reaction score
10
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.).
 
Last edited:

bjs.pdx

Member
Joined
Oct 6, 2018
Messages
39
Reaction score
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.
 

sh0tsmash

New Member
Joined
Jul 8, 2014
Messages
15
Reaction score
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)
 
Last edited:

sortons

Member
Joined
Aug 9, 2018
Messages
60
Reaction score
10
@Andreas, glad to hear that pjsip works for you - could you please share your setup/settings?
 

l4cky

Member
Joined
Jan 27, 2015
Messages
175
Reaction score
4
Anyone looking for PJSIP configuration info might want to take a look at https://twosortoftechguys.wordpress...s-a-gateway-between-google-voice-and-freepbx/

It is an update of an older article that they rewrote with PJSIP instructions.

even the new version 16-15 doesn't fix th pjsip problem?

Quick question: Should the internal extensions such as 101 set as chan_sip if the Trunk SIP is chan_sip type? Or it has nothing to do, and we can mix pjsip for internal extensions and use SIP CHAN as trunk?
 

Members online

Forum statistics

Threads
25,778
Messages
167,504
Members
19,198
Latest member
serhii
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top