|
MurrayB
|
 |
« on: August 04, 2012, 03:52:30 pm » |
|
I am configuring a Nexus 7 with the Obion for Android. I successfully downloaded the app and was able to do the echo test.
I configured the soft phone gateway to an Obi 110. The name I gave to the soft phone shows up on the app. I was also able to call one of my Obi 110 via Obitalk using **9. I tried to call a PSTN both 10-digit direct and with **2+10-digit with no luck. The display shows ready, calling, and peer ringing. I hear the ring in the speakerphone but the called phone does not ring.
I have no Circle of Trust and the AA is disabled.
I must be doing something wrong.
Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #1 on: August 04, 2012, 04:09:56 pm » |
|
I tried to call a PSTN both 10-digit direct and with **2+10-digit with no luck With your Obi110 set as the default gateway for your Obion app you should be able to just dial from the app the same as from the phone connected to the Obi.
Default settings only allow for calling through the trunk that is designated as primary for outgoing calls. To use other trunks you must set up single stage dialing through any Obi trunk.
RonR put together a single stage dialing configuration for this purpose. Read this post and follow the link at the end of it. http://www.obitalk.com/forum/index.php?topic=3094.msg20656#msg20656
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #2 on: August 04, 2012, 05:15:07 pm » |
|
Hi jimates thanks for your prompt reply.
"I tried to call a PSTN both 10-digit direct and with **2+10-digit with no luck." - I thought that 10-digit direct would act as dialing direct from the phone which is default on SP2. When that did not work I tried **2.
I want to continue to use the default trunk which is SP2 just like I dial from the attached phone.
I hope that this helps to clarify my situation.
|
|
|
|
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #3 on: August 04, 2012, 06:56:28 pm » |
|
You must assign the app a default gateway. If you haven't done this; from your dashboard, click on the app and make sure the Obi is selected as the gateway. When you sign in to the app on your Nexus 7 and click on the Obitalk icon it will show you the "voice gateway" that it is using.
If you only want to call using the default trunk you should just dial from the app the same as you do from the phone attached to the Obi.
I have used the app on many different devices without a problem, but others have had trouble.
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #4 on: August 04, 2012, 07:27:26 pm » |
|
The default gateway is assigned the proper 200xxxxxx shows up on the app as the Voice Gateway.
My OBiTALK number on the app is the Soft Phone number now on the dashboard as Nexus 7.
I can call to another Obi through the gateway via **9200xxxxxx but I can't reach a reach a regular phone. On the app I have ready, calling, and peer ringing. I hear ringing on the app but not the phone.
What next?
Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #5 on: August 04, 2012, 08:10:10 pm » |
|
dialing **9200xxxxxx is just a call placed to another Obi endpoint using the Obitalk service. A gateway is not needed or used when calling other Obi endpoints from the app.
What does the call history in the Obi show when you try to call a regular phone from the app.
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #6 on: August 05, 2012, 07:36:23 am » |
|
Hello Again
This is weird. I initially had set up a remote Obi110 as the gateway. I changed the gateway to the local Obi 110 at my present location so I could access call history. What happened is interesting.
I dialed my cell phone from the Nexus 7 and the phone connected to the local Obi rang. The call history:
Call 108/05/2012 08:49:03 Terminal ID OBiTALK1 PHONE1 Peer NameNexus 7 Peer Number290xxxxxx DirectionInbound Inbound 08:49:03Ringing 08:49:12Call Connected 08:49:18End Call (I lifted the handset)
I wonder if the remote Obi rang during the previous tests. The two Obi fork to each other. I would expect if the remote Obi rang during my previous tests if the calls should have been forked here as well.
I will be at the other location tonight and I will post the call history from yesterday’s tests tonight or tomorrow morning. What do you think about this mornings test?
Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #7 on: August 06, 2012, 04:03:25 am » |
|
All of the other calls attempted through the originally assigned remote gateway look like this:
Terminal ID OBiTALK1 PHONE1 Peer Name Nexus 7 Peer Number 290xxxxxx Direction Inbound Inbound 22:34:06 Ringing 22:34:25 End Call
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #8 on: August 06, 2012, 04:51:09 pm » |
|
hello jimates
I rechecked my setup tried another call with the call gateway set as the Obi at my location and the phone attached to the Obi rang and not the number that I called.
Call 1 08/06/2012 19:41:46 Terminal ID OBiTALK1 PHONE1 Peer Name Nexus 7 Peer Number 290xxxxxx Direction Inbound Inbound 19:41:46 Ringing 19:41:55 End Call
I think that I am doing everything right but may be missing something. I am also willing to concede that the app won't work with this Tab but everything appears to be proper. I was hoping to use this in Europe shortly.
I look forward t your latest analysis.
Thanks!
|
|
|
|
|
Logged
|
|
|
|
AndyA
Newbie

Posts: 43
|
 |
« Reply #9 on: August 06, 2012, 06:34:31 pm » |
|
How do you check the call history on the OBi? I tried to walk through the OBi Dashboard and can find where it might be selected.
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #10 on: August 06, 2012, 07:19:17 pm » |
|
You won't find it through the ObiTalk dashboard. You have to log directly onto the Obi.
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #11 on: August 07, 2012, 04:08:42 am » |
|
Looking at the Obi I want to use as the gateway the ObiTalk provisioning is disabled and the ObiTalk inbound call route is set to default ph. Does this have anything to do with the problem using the Android?
|
|
|
|
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #12 on: August 07, 2012, 05:14:12 am » |
|
Looking at the Obi I want to use as the gateway the ObiTalk provisioning is disabled and the ObiTalk inbound call route is set to default ph. Does this have anything to do with the problem using the Android?
When you set the default gateway for a softphone number, Obitalk configures your Obitalk Service settings to allow an app to use it as a voice gateway. It does the same thing when you add numbers to your circle of trust. If Obitalk provisioning is not enabled then it can not do that. Of course you can always do it yourself. Your Obitalk Service inboundcallroute (when configured by Obitalk) would look like this {(290xxxxxx)>(xx.):SP1},{(290xxxxxx):aa},{ph} This says, 1 - any incoming call from 290xxxxxx that includes a valid phone number, that included number will be delivered using SP1. 2 - any incoming call from 290xxxxxx without an included number, will be deliverd to the AA. 3 - all other incoming calls will ring the phone port.
|
|
|
|
« Last Edit: August 07, 2012, 05:19:35 am by jimates »
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #13 on: August 07, 2012, 07:26:30 am » |
|
Hi jimates - thanks for the reply
I figured that the app appeared to be working and review of the call history indicated that the calls were ending with the Obi. I thought that, whoa, the Obi was set to be configured locally that may be the problem.
In trying to understand: Does this entry remain (xx.): I do not understand what entry this would be
This is great I await your reply.
Thanks so much!
|
|
|
|
« Last Edit: August 07, 2012, 07:47:40 am by MurrayB »
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #14 on: August 07, 2012, 09:29:11 am » |
|
Once a voice gateway is set for the app, all calls (except Obitalk calls direct to endpoints) go through the designated Obi pretty much as if they were dialed from the phone port. Anytime you dial any number that isn't an Obitalk endpoint the call is processed according to the rules of the Obitalk Service outbound call route. (xx.): is the part of the rule indicating a phone number.
Withe the included rules (from the app) a valid number is delivered using the designated trunk. Any other key press is delivered to the AA.
With the only rule being "PH", all incoming calls were only ringing the phone port. With provisioning turned off, Obitalk could not change the call route for the default gateway.
|
|
|
|
|
Logged
|
|
|
|
|
MurrayB
|
 |
« Reply #15 on: August 07, 2012, 01:36:40 pm » |
|
OK jimates we have success on this front. I can reach the Tab through ObiTalk and place calls.
I now have to figure out how to make the Bluetooth work with the app. I probably will try a new thread if there are no takers and check out other forums.
Thanks Again - this is great. I am glad that you gave me time to figure out that provisioning was probably the answer after letting the call history sink in!
All the Best!
|
|
|
|
|
Logged
|
|
|
|
|
jimates
|
 |
« Reply #16 on: August 07, 2012, 02:52:48 pm » |
|
Glad to help.
|
|
|
|
|
Logged
|
|
|
|
AndyA
Newbie

Posts: 43
|
 |
« Reply #17 on: August 07, 2012, 07:40:41 pm » |
|
Glad to see MurrayB's problem fixed. I have a Nexus 7 too and have slightly different problem. I have another post too (see here: http://www.obitalk.com/forum/index.php?topic=3798.0) but no luck getting response. I'm able to receive calls with no problem but cannot complete a call to my own OBi and gateway pass through to another number. The call from my OBiON to the OBi110 is not answered by Auto Attendant and the call by gateway pass through to another number makes connection but we can not hear each other. The lesson learned from this post seems to not apply to me since I checked the syntax of InboundCallRoute and I'm able to make a gateway connection - we just can't hear each other. Could I possibly have other setting wrong?
|
|
|
|
|
Logged
|
|
|
|
|