May 26, 2019, 08:26:08 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Experiences using WebRTC (Call OBi) as Alternative to OBiOn  (Read 4545 times)
nh905
Newbie
*
Posts: 14


« on: May 17, 2019, 11:54:28 am »

I have an OBi200 using Anveo as my VoIP provider.  I can make and receive calls to local and international numbers without any issues.  When travelling with a WiFi connection, I used OBiON (Android) to connect with my OBi200 to avoid roaming charges.  OBiON stopped working on Android 7.  I tested the Call OBi button on OBiTALK back in 2017 with variable results - it would often take multiple attempts to get through.

When I tested again this March, I could connect via Chrome (current version, Windows 10 Home) and had two-way audio but the connection would consistently drop after 30 seconds.  The Obi200 Call History shows the call ending but does not provide any hint as to the reason.  I tested with private/incognito sessions and also tried Chrome on Android with the same result.  I could connect via Firefox, the connection stayed up, but I could not hear, nor could the receiving party hear me speaking. 

I tried again yesterday (May 16th) and today - this time I see "Starting Call" immediately followed by "Call Ended".  The OBi200 Call History suggests that the call never connected.  I have also created a support ticket to see if the Call OBi feature is broken.

On a whim, I fired up my Galaxy S4 that is still on Android 5.  I was able to call through to my landline but could not hear or be heard.  If I call my OBi200, I usually get the Attendant, but it is not picking up any key presses.  Once it rang through to the phone line connected to the OBi200: I could hear and be heard, although the volume on the OBi200 phone line was very weak. 

I appreciate that OBiON is no longer supported, and WebRTC is the way to go.  Are there configuration options on the OBi200 that I should be investigating?  The configuration was originally done on an OBi110 and restored to the OBi200.  I can try to factory reset the OBi200 although it took me a while to get the OBi110 working properly with Anveo.

Thanks, Norbert

Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3827


« Reply #1 on: May 17, 2019, 10:45:32 pm »

I believe Anveo supports multiple extensions. Register a softphone on your Android as a 2nd Anveo extension. Now just call your main extension from your Android. I'm not familiar with Anveo, so someone else will have to show you how to do this.
Logged
nh905
Newbie
*
Posts: 14


« Reply #2 on: May 21, 2019, 09:54:44 am »

@azrobert, I am looking at getting a new SIP account to support a softphone app on my Android phone.  It looks like I can add an additional SIP to my OBi200.  Not sure I can add a sub-account to Anveo without upgrading from my Basic account. 

I was hoping to 'keep it simple'.  OBiON worked surprisingly well while travelling, although I ran into a few Internet providers that blocked required ports (solved by a VPN).  I even got OBiON working once using my Galaxy S4 yesterday.  Subsequent attempts connected but I could not hear or be heard.  Call OBi still is not working for me at all.  I created a support ticket but have not heard back. 

Thanks, Norbert
Logged
nh905
Newbie
*
Posts: 14


« Reply #3 on: May 22, 2019, 04:17:27 pm »

I am making progress.  I signed up with https://www.onsip.com/getonsip and obtain SIP accounts for my laptop, my phone, and my OBi200.  On my phone, I am using the OnSIP Android app.  I was able to make calls between my laptop and my phone - no issues with connecting, reasonable voice quality (my Internet is not the best).  I even figured out how to call my OBi200 from my laptop/Android phone by adding 1555 in front of my Anveo account@sip.anveo.com - the calls rang through to my second line that is plugged into the OBi200.

My goal is to get to the OBi Attendant from my SIP softphone so that I can enter a new number.  I could probably figure out how to write routing rules based on the source ID of the caller.  However, I decided to "keep it simple" and associate SP3 with the third OnSIP account that I had defined.  Initial testing was promising: from my laptop, I could call the OBi200 OnSIP account and have it ring through to my second line.  I updated the X_InboundCallRoute to specify AA rather than ph.  Calling from my laptop, I was able to interact with the Obi Attendant and place a call via Anveo to multiple phone numbers. 

When I called from my Android phone, I was able to get to the OBi Attendant and I could call through to my second line on the OBi200 by pressing '1'.  I could get the OBi Attendant to request a new phone number by pressing '2', but the call got disconnected.  Checking the OBi200 Call History, it appears the OBi Attendant never attempted to connect to the 'new call' number. 

I thought it might be the OnSIP Android app and switched to ZoiPer, but this was even less successful - I could see the connection between my phone and the OBi200 via the OnSIP dashboard but never got the OBi Attendant voice prompts.  On a few occasions, pressing '1' a few times caused line 2 to ring but I could not hear or be heard.

I will try to login to my Android phone SIP account from my laptop to narrow down if there might be difference between my primary SIP account (assigned to the laptop) and the secondary accounts (my phone and the OBi200.  I will also dig into digit maps and call routing.

Regards, Norbert
Logged
nh905
Newbie
*
Posts: 14


« Reply #4 on: May 24, 2019, 04:25:40 pm »

I tested the Android OnSIP account using the OnSIP.com web interface and successfully interacted with the OBi200 Attendant.  I enabled logging on the OBi200 and traced activity when calling the OnSIP account associated with SP3.  When I called from my laptop, I saw "May 23 13:50:43 obi200  obi200: [JB] DTMF (RX) RFC -- DGT: 1, ts: 547780, seq: 28329, ooo: 0, size: 4" for each of the key presses of the number I wanted the OBi200 Attendant to call.  However, when I called from my phone using the OnSIP Android app, I got a very different trace entry where the DTMF code is near the end (Signal= 1).  I am guessing that the OBi200 Attendant does not know how to interpret this format and hangs up. 

Quote
May 23 14:05:36 obi200  obi200: INFO sip:obi200@xx.xx.xx.xx:5082 SIP/2.0#015#012Record-Route: <sip:199.7.175.104;lr;ftag=r64v61mvef;did=e12.f6fb4347;ns=1;pr=3;pr=3>#015#012Record-Route: <sip:199.7.173.103;lr;ftag=r64v61mvef;did=e12.0a295564;nc=1>#015#012Record-Route: <sip:199.7.173.183;r2=on;lr;ftag=r64v61mvef>#015#012Record-Route: <sip:199.7.173.183:443;transport=wss;r2=on;lr;ftag=r64v61mvef>#015#012Via: SIP/2.0/UDP 199.7.175.104:5060;branch=z9hG4bK4787.6f892f7.0#015#012Via: SIP/2.0/UDP 199.7.173.103:5060;branch=z9hG4bK4787.2e5fdb85.0#015#012Via: SIP/2.0/UDP 199.7.173.183:5060;branch=z9hG4bK4787.2ee62756.0;i=3c93d3f#015#012Via: SIP/2.0/TCP 4l03h59lc90s.invalid;rport=18099;received=209.171.9.37;branch=z9hG4bK4063496#015#012Max-Forwards: 67#015#012To: <sip:obi200*xx.xx.xx.xx!5082_n@199.7.175.104;gr>;tag=SP34f75d9afff52985#015#012From: "xxx xxx" <sip:xx@xx.onsip.com>;tag=r64v61mvef#015#012Call-ID: i3j673tf04nojd7snqm7#015#012CSeq: 6895 INFO#015#012Supported: 100rel, replaces, outbound#015#012User-Agent: SIP.js/0.13.8 OnSIP/1.10.3.81/android#015#012Content-Type: application/dtmf-relay#015#012Content-Length: 24#015#012P-WS: 1#015#012#015#012Signal= 1#015#012Duration= 100

I suspect calling from the laptop uses WebRTC which may explain the different data format.  I used Chrome on my phone to access OnSIP.com and place the call - it does work but the keypad intermittently hangs causing key press errors.  I have not found a WebRTC client for Android other than ones I need to build myself.

I have tried a number of free SIP clients but only OnSIP appears to get a response from the OBi Attendant and have the Attendant respond to even the first key press (1, 2, or 3).  MizuDroid appears to have a DTMF setting but I cannot get it to register with OnSIP.com (working with the developers). 

The journey continues...  Norbert
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3827


« Reply #5 on: May 24, 2019, 04:55:17 pm »

See:
http://www.obitalk.com/forum/index.php?topic=15920.0

The OP currently doesn't have PSTN service, so wasn't able to make a call. He was able to connect to the AA and enter an outbound number.

PBXes.com has a function (Sub-PBX) that doesn't require the OBi Auto Attendant. An account will cost a one-time $15 fee. This function worked for me.
Logged
nh905
Newbie
*
Posts: 14


« Reply #6 on: May 25, 2019, 09:50:01 am »

@azrobert, I will re-install Zoiper and do more testing with OBi200 logging enabled.  With the OnSIP Android client, I am connecting to the AA and it will accept the first key press (1, 2, or 3).  Pressing 1 rings my locally attached phone, pressing 2 or 3 prompts me to enter a phone number, but the AA either does not recognize the dial tones or does not set up the new call.  Everything works fine when I use the OnSIP WebRTC client.  The log shows that the DTMF codes arrive but I have not figured out how to enable logging of the AA actions.  The logs are quite verbose and not easy to read.

I am working with the MizuDroid developers to get their Android client working with OnSIP - it appears to support various DTMF schemes.  Mizutech also has a Webphone package that may allow me to set up a local 'Call Obi' button where I can enter the destination number and have the Webphone automate calling my OBi200. 

Thanks, Norbert
Logged
nh905
Newbie
*
Posts: 14


« Reply #7 on: May 25, 2019, 11:03:57 am »

@azrobert, I recall looking into PBXes.com some years ago and getting thoroughly confused, although I can check it out again. 

You got me thinking about what kind of features Anveo has as part of its Call Flow Builder.  It turns out that calling my Anveo phone number and entering in a magic incantation allows me to start a new call.  Unfortunately, calling my Anveo SIP address immediately rings through to the phone attached to my OBi200 instead of following the Anveo call flow.  Maybe it is as simple as routing my SP3 voice service for incoming OnSIP calls to my SP2 service associated with Anveo.

I need a 'Dummies for Internet Telephony' (:-).  Actually, there is one published in 1997 and out of print.

Thanks, Norbert
Logged
nh905
Newbie
*
Posts: 14


« Reply #8 on: Today at 07:51:55 am »

@azrobert, success!  I finally got MizuDroid to authenticate with OnSIP (the setup is not obvious), was able to connect to my OBi200, and MizuDroid sent the keypad DTMF tones in a language that the Auto Attendant understood.  MizuDroid has five different DTMF options, but 'Auto' worked for me.

I am trying to get up to speed on SIP and the OBi200 and will test out some other options when I get a chance.  What would be great is an app that does what 'Call OBi' used to do - accept the destination phone number and do the connection to the OBi200 under the covers.

Thanks, Norbert

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC