Hi,
I initially want to achieve two things by my Obitalk200. Need help from members & support to achieve it.
1- Unconditional Forwarding of incoming calls on my Obitalk + Google Talk + PSTN line (connected with ObiLine) to my one GSM number via Obi-Bluetooth.
*I have a mobile phone connected to Obitalk via Bluetooth dongle.
2- Calling mobile paired with ObiTalk200 from my mobile ...and then dialing out (via Google Talk OR PSTN line OR ObiTalk) to a remote ObiTalk200 (which is connected with PSTN line via ObiLine) and then making calls via remote PSTN.
2nd Scenario more in detail that I want to achieve.
Mobile Phone in hand calling ....> Mobile Phone paired with ObiTalk ...>unconditional dialing to remote ObiTalk200 connected with PSTN line (via ObiLine) ...getting dial tone ....Dialing out number.
Please help to achieve this, if possible ..step by step.
Many thanks :)
Johny.
1- I'm not sure what you want. Do you want to forward inbound PSTN calls using your mobile connected via BT to another number? If yes:
Physical Interfaces -> Line Port
CallForwardUnconditionalEnable: Checked
CallForwardUnconditionalNumber: bt1(14808370001)
The OBi doesn't really forward the call. It bridges the call out another trunk and makes a new call, so the person receiving the call will see the callerid of the mobile connected via BT.
2-
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):pp(510222222*9)},{ph,ph2}
Change 4808370001 to your mobile's callerid
Change 510222222 to the OBi number of the remote OBi.
Remote OBi:
Voice Services -> OBiTalk Service
Add to the beginning of the InboundCallRoute:
{510111111>(<9:>):li},
If the only rule in the InboundCallRoute is "ph" do this:
{510111111>(<9:>):li},{ph}
Change 510111111 to the OBi number of the local OBi.
azrobert,
Thank you for your help. I think I have been able to explain 2nd scenarion and will try after setting it up.
For 1st scenario I want to transfer all incoming calls on local ObiTalk (Google Talk, PSTN and other VoIP calls) to my GSM number. For that I have another mobile phone paired with ObiTalk and having an unlimited calling out plan for GSM number I carry. So can I route all incoming calls to GSM network ? I think you mentioned for PSTN line only, how to achieve this for GV and any VoIP service, can you please help.
All the trunks have the same options.
Do the same as the Line port for each trunk.
They are found at:
Voice Services -> SP1 thru SP4 Service
You can get the original inbound callerid If you don't mind running an SIP softphone on your receiving mobile. You would not use your mobile connected to BT.
It's a more difficult setup, but not that much more. If you are interested tell me if you have an SIP provider (non GoogleVoice) defined and what SP you used for the definition.
Edit:
You need a data plan on your mobile.
Quote from: azrobert on January 06, 2015, 02:10:20 PM
All the trunks have the same options.
Do the same as the Line port for each trunk.
They are found at:
Voice Services -> SP1 thru SP4 Service
I did it for SP1 (considering it is GV probably ?). Please see image below, I called my GV number but call doesn't go on my forwarding number via Bluetooth mobile. In fact it keeps ringing and finally goes to voice mail.
Does the call actually reach your OBi? Check in the Call History. That is under Status in the local web interface.
Actually my DECT cordless was in energy saving mode & wasn't ringing for some time, but on direct calls on GV it rings immediately.
For diverting GV calls to my GSM number via a Bluetooth paired phone I have entered settings as you advised but calls are still ringing on cordless attached with ObiTalk with caller ID showing forwarding number. Can you advise what might be the issue?
Try a different method.
Set CallForwardUnconditionalEnable and CallForwardUnconditionalNumber back to default.
On the same configuration page for SP1:
X_InboundCallRoute: bt1(0657567588)
Actually without any forwarding GV rings on ObiTalk but with even last forwarding method it doesn't work :(
Do you have an entry in the OBi call history for the last call?
To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column.
Then click Call History.
Here is the call history:
From GT1() To BT1(0657567588) Call Connected
It worked :D
I am trying it again and will share experience here, earlier I was using tablet with phone function and was using a VoIP service to call my GV number (which was having my GV number as CallerID).
It worked with Samsung S4 as paired phone, trying with available BT phone, trying to call again and again to test. Thanks a million.
Quote from: azrobert on January 06, 2015, 12:22:31 PM
2-
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):pp(510222222*9)},{ph,ph2}
Change 4808370001 to your mobile's callerid
Change 510222222 to the OBi number of the remote OBi.
Remote OBi:
Voice Services -> OBiTalk Service
Add to the beginning of the InboundCallRoute:
{510111111>(<9:>):li},
If the only rule in the InboundCallRoute is "ph" do this:
{510111111>(<9:>):li},{ph}
Change 510111111 to the OBi number of the local OBi.
I am trying to achieve the 2nd part, but I want to use some other VoIP service to bridge calls (searching for a TLS provider due to VoIP blockage issues here). I have ordered 2 Freetalk adapters to use Skype to route calls as Skype is open on both local and remote sites. I ordered Freetalk as was advised to use it here on forum but now I can't recall how would this help with a ObiLine.
If I want to use remote mobile paired with remote Obi and connected with Freetalk Skype adapter connected with Obi with Obiline (so route calls over Skype somehow instead of standard voip or GV) can I achieve this ?
If they are blocking by port number you can change the ports on the obi.
I've never worked with TLS and don't know any TLS providers.
I know what Freetalk is, but I never used one.
You can connect the local FreeTalk to an OBiLine adapter.
The remote OBi already is using the OBiLine adapter and I don't think you can connect a 2nd.
You could buy an OBi110 for the remote site.
The remote site would look like this:
FreeTalk -> OBi110 -> OBi200 -> OBiLine -> PSTN
I did setup something like this without FreeTalk for someone on the forum.
I'll see if I can find the thread latter.
There is a free Skype Gateway.
It runs on a computer with an active Skype session and can communicate with an OBi.
It can replace FreeTalk and the OBi110 at the remote site.
It can also be used at the local site.
It runs on different platforms, but I've only used the Windows version.
I am not sure if pbxes or sipsorcery will work but I will give it a try.
If I manage to route calls between local and remote obi on skype using FreeTalk plugged in ObiLine on both ends that would be awesome. But at the same time I want to use remote GSM connected with Bluetooth to remote obi....and some calls to ring on phone port of remote obi.
I am not sure if this all can be achieved?
You won't be able to pass a number to the remote site using Skype.
The only way I know how to accomplish your requirements is to use the Auto Attendant at the remote site to determine routing.
You definitely can only have 1 OBiLine connected to the OBi200, so you will need an OBi110.
Your setup would look like this:
OBi200>OBiLine>FreeTalk>Skype>FreeTalk>OBi110>OBi200>AA>
OBiLine>PSTN
OBiBT -> Cell
Phone Port
I helped someone with a setup like this:
OBi202>OBiTalk>OBi202->OBi110>PSTN
This is the closest I came to the above setup, but it should work.
I didn't know SipSorcery and PBXes supported TLS.
SipSorcery would greatly reduce the complexity.
It would look like this:
OBi200>SipSorcery>OBi200>OBiLine->PSTN
OBiBT -> Cell
Phone Port
Using SS you can pass a number to the remote OBi200 and determine routing based on that number. I have an SS account, so I can help with the dialplan. I tried connecting my OBi to SS using TLS and it failed. I just changed the transport method to TLS and the registration port to 9712. Don't know if additional changes are required. I have a Free SS account, so maybe TLS is not supported with these accounts.
I don't know how to do the same with PBXes. You would have to use the AA to determine routing.
I tried registering with SipSorcery with TLS transport again and it worked!
I tried using registration port 5061 this time.
There is a TLS bug at SipSorcery, but when it happens they automatically restart the server.
I saw a post on their forum.
I don't know if this bug has been fixed.
If you want to use SipSorcery it would be a very easy setup.
Each OBi200 would register at SipSorcery as an extension.
Then you could do something like the following:
Dial 0 to ring the remote OBi200
Dial 9 to get dial tone on the remote PSTN
Dial 9 + a number (98005551212) to call out on the remote PSTN
Dial a number with a different prefix to call out the remote BT.
If you want to go the route, tell me what prefixes you want to use and the format of the outbound number.
SipSorcery cost $69 per year.
http://www.sipsorcery.com/mainsite/Home/Pricing
The no longer offer free accounts.
I believe they have a 30 day money back guarantee.
Thank you for your reply.
I used SS till last year, forgetting if it was working on different ports in this restricted VoIP zone. But as SS doesn't handle media it has less capability to bypass restrictions to my understanding.
So If I renew my SS will I use it with AA? I am wondering if I call paired BT phone with local Obi from my mobile will AA attend this call And then SS will route it to remote Obi (also connected with PSTN & BT Phone) giving me a dial tone ?
Before renewing SS I am wondering if this all can be easily achieved.
I can recall that PBXES was able to somehow bypass restrictions than SS.
I lied to you about PBXes.
I forgot about a function they have, so you can so the same as SipSorcery.
I have to refresh my memory on how it works.
I tried to register to PBXes using TLS and port 5070 and it failed.
I changed it to UDP and port 5060 and it registered, so I have the credentials correct.
You might have to figure out how to register to PBXes.
I have a free account and I don't know if TLS is included.
For both SipSorcery and PBXes:
You don't need the AA at the remote site.
From the local phone port you don't need the AA locally.
If you want to call the cell attached to the local BT then you need the local AA.
FYI, when I was testing PBXes the latency was horrible.
I found I was registering to their European server.
Switching to the west coast server improved the latency, but it was still noticeable.
This was a long time ago.
I don't know if anything has improved.
I don't know where your sites are, but you might have latency problems.
I will try now with PBXES but can AA help me to have dial rules? Like:
1- Calling remote Obi and getting a dial tone of PSTN and/or use remote BT phone ?
2- Call phone connected with local Obi and then getting call transferred to remote Obi and do the above number 1 ?
3- Getting all calls on remote ObiBT transferred to local Obi and then via local ObiBT to my mobile ...unconditionally ?
Thanks a lot :)
The AA can only route a call to a trunk.
An inbound call can be routed to the AA unconditionally or by callerid.
The following assumes PBXes is defined on SP1 on local and the remote OBi.
This is how it would work:
Quote2- Call phone connected with local Obi and then getting call transferred to remote Obi and do the above number 1 ?
You want to dial number 123456 on the remote PSTN or get dial tone.
You call the local BT phone.
You are sent to the AA.
You will get a prompt
You enter 2 for a new call
You will get another prompt for the outbound number
You enter 9123456 or 9
I chose the 9 prefix
The call is sent to SP1 (PBXes) because the AA primary route is SP1
The remote OBi will receive the call on SP1 with the dialed number.
The SP1 X_InboundCallRoute will have rules based on the 9 prefix to send 123456 to PSTN or get PSTN dial tone
Quote3- Getting all calls on remote ObiBT transferred to local Obi and then via local ObiBT to my mobile ...unconditionally ?
You can do this without the AA
Quote1- Calling remote Obi and getting a dial tone of PSTN and/or use remote BT phone ?
Yes, but I don't understand how are you calling the remote OBi?
Here is an example how PBXes can route a phone number to an OBi.
http://www.obitalk.com/forum/index.php?topic=5411.0
In this example the iPhone is registered as an extension and the OBi as a Sub-PBX. The iPhone is sending outbound numbers to the OBi.
You want to send outbound numbers in both directions, so both OBi's will be setup as a Sub-PBX.
The above post is almost 2 years old and that is the last time I used PBXes, so I have to refresh my memory on how Sub-PBXes work.
I tried PBXES on Bria for Andriod and PC but voice quality is worst ever and latency is very high, in fact you can't recognize each other.
As I am in VoIP censored area on both local and remote site and good thing is that GV and Obitalk works, though GV quality is better. Can you please help me to configure local and remote devices (step by step with syntax/dialing rules?) using AA or a direct way to achieve it. I will try yo summarize again what I want to achieve:
1- I want to receive all remote calls from remote ObiBT/Obi/GV/Other VoIP provider (in another country) on local Obi (paired with a mobile phone) and then transferred to my mobile which I carry with me anywhere.
2- I want to call local ObiBT and then reach remote ObiBT and remote ObiLine to call out.
3- I want to be able to call remote Obi sometime using local obi (either Obi-Obi Or GV-GV or other SIP-SIP), speed dials will help.
Thank you very much. :)
I'm leaving shortly and will be back in a few hours.
I don't have time to re-read this thread to see what we did.
Is the last post your complete requirements or do you also need something we did previously?
As SS or PBXES aren't options due to VoIP blockage AA is only option with GV/ObiTalk service.
From last posts I managed to transfer calls on local SP1 (GV) calls to my mobile via local ObiBT. Rest which I mentioned in 2nd last post are pending. I see you only help so far.
Thank you.
Johny.
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):aa)},{ph,ph2}
Change 4808370001 to your mobile's callerid
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|XX.)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(<510222222*>XX.):pp}
Physical Interfaces -> Phone Port
DigitMap
(2*(XX.)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
{(<2:510222222>*(XX.)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Speed dials:
pp(510222222*0) Ring phone
Speed Dial #9 pp(510222222*9) Line dial tone
pp(510222222***708005551212) Line call
pp(510222222*8005551212) BT call
Remote OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111>(<0:>):ph},{510111111>(<9:>):li}},{510111111>(<**70:>XX.):li},{bt1}
Change 510111111 to the OBi number of the local OBi.
Change 510222222 to the OBi number of the remote OBi.
Phone Port Settings - Bold is what I changed.
All XX. are upper case.
Upper case X includes a star.
From phone port dial:
2*0 Ring phone
2*9 Line dial tone
2***708005551212 Line call
2*8005551212 BT call
From AA:
Reply 1 to ring phone port
Otherwise reply 2 then:
9# Line dial tone
**708005551212# Line call
8005551212# BT call
I used prefix **70 (default for local line port) to route calls to the remote line port.
You can change it to anything you want, even a single digit.
It must not match the beginning of any BT outbound numbers.
Hopefully I didn't make any mistakes, but expect errors.
Edit:
The Phone Port OutboundCallRoute was modified after the original post.
Mpli was changed to XX.
The XX. in the remote OBiTalk InboundCallRoute was lower case, changed to upper case.
The remote OBiTalk InboundCallRoute is a replacement, not to be added to the beginning. Text has been changed.
Added Speed Dial check in AA DigitMap. This really isn't needed because XX. will validate Speed Dials.
Assigned pp(510222222*9) to Speed Dial #9
I didn't like my setup. Dialing from the phone and AA are now more consistent. Change the "#" line prefix to anything you want. I removed the line dial tone option.
Local OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510222222>(xx.):bt1},{ph}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{+ccmmmmmm:aa},{ph}
Change cc to the country code
Change mmmmmm to your mobile's CID
Change 4808370001 to your mobile's callerid
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(1xxxxxxxxxx):sp1},{(<510222222*>@@.):pp}
Physical Interfaces -> Phone Port
DigitMap
(***|1xxxxxxxxxx|@@.S2)
OutboundCallRoute
{***:aa2},{(1xxxxxxxxxx):sp1},{(<510222222*>@@.):pp}
Speed dials:
pp(510222222*0) Ring phone
pp(510222222*#8005551212) Line call
pp(510222222*8005551212) BT call
Remote OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111>(<0:>):ph},{510111111>(<#:>xx.):li},{510111111>(xx.):bt1},{ph}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
pp(510111111*Your_Cell#)
Physiscal Interfaces-> Line port -> InboundCallRoute:
pp(510111111*Your_Cell#)
Change 510111111 to the OBi number of the local OBi.
Change 510222222 to the OBi number of the remote OBi.
From local phone port dial:
0 Ring remote phone
#8005551212 Remote Line call
8005551212 Remote BT call
18005551212 Local SP1 call
From AA after calling BT with your mobile:
Reply 1 to ring remote phone
Otherwise reply 2 then dial:
#8005551212# Remote Line call
8005551212# Remote BT call
18005551212# Local SP1 call
Thanks a million ;D
I will give do setting and will give my feedback. Even if it doesn't work I really appreciate your time helping me with this, you have no idea how much it is gonna help me indeed to reach my family back home.
You can try GV to GV If OBiTalk network doesn't work or to compare the 2 methods.
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?Your_Cell#):sp1(Remote_GV#)},{ph}
Speed dial:
sp1(RMT_GV#)
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#):aa},{ph}
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(<0:>):ph},{(<#:>xx.):li},{bt1}
Speed dials:
li(8005551212) Line call
bt1(8005551212) BT call
From local phone dial the remote GV speed dial or GV number and you will be connected to the remote AA.
Inbound BT calls will be automatically connect to the remote AA.
From remote AA:
Reply 1 to ring remote phone
Otherwise reply 2 then:
Speed Dial#
#8005551212# Line call
8005551212# BT call
You can have both methods setup at the same time.
Leave the BT Inbound route unchanged like this.
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):aa)},{ph,ph2}
If you want to use the GV method, enter the remote GV speed dial from the AA.
I have configured it as you advised, calling from GV and Obitalk to remote Obi rings on remote attached phone but calling from remote GV or ObiTalk to local GV/ObiTalk doesn't work. On ObiTalk it beeps-beeps and on GV it goes to voice mail.
I am using speed dial numbers to call. So far I have tried calling local GV number from a mobile and getting it transferred to my local mobile via BT. Both local and remote Obi deivces are with me to configure before I send it to my home country. Full testing is pending due to ObiBT not being compatible with available Nokia phones. I will have to buy some dedicated Samsung phones.
I think there is some issue with remote Obi calling configuration ? Is current configuration transfering all calls from remote Obit to local Obi to my mobile via local BT ? Please help.
Regards.
Johny.
Please display the call history from both OBi200s for the OBiTalk call for the failing call.
Also post from the local OBi200 the following.
Can you successfully call the local OBi200 with another phone?
I update the configuration in reply#27 above.
I added in BOLD code to route remote inbound BT calls to your cell via local BT.
Try the failing call again after making the above change.
Quote from: azrobert on January 19, 2015, 08:54:06 PM
Please display the call history from both OBi200s for the OBiTalk call for the failing call.
Also post from the local OBi200 the following.
In remote Obi Call History is below:
01:59:53 From PH1 To PP1(ob510946XXX)
01:59:57 Call Ended (486 Busy Here)
&
01:58:40 From PH1 To GT1(2347383XXX)
01:58:41 Ringing
01:59:07 Call Connected
01:59:16 Call Ended
But in GV it goes to voice-mail.
---
In local GV call history is below and it rings on remote Obi:
00:49:33 From PH1 To PP1(ob510813XXX)
00:49:37 Ringing
00:49:41 Call Connected
00:49:51 Call Ended
&
00:09:35 From PH1 To GT1(2345640XXX)
00:09:36 Ringing
00:09:42 Call Connected
00:10:19 Call Ended
And it rings on remote Obi.
Quote from: azrobert on January 19, 2015, 08:54:06 PM
Can you successfully call the local OBi200 with another phone?
I tried calling local GV from a mobile phone but it doesn't ring on local Obi. I tried calling remote GV number from my mobile and it rings.
Quote from: azrobert on January 19, 2015, 08:54:06 PM
I update the configuration in reply#27 above.
I added in BOLD code to route remote inbound BT calls to your cell via local BT.
I have copy pasted without any change, I hope it is correct ? Still it is same.
Yet another issue is that when from my mobile phone I call local ObiBT it rings on phone connected with local Obi and doesn't connect me with remote Obi AA. In fact Obi Connected phone shows Caller ID with country code and "+" in start while in Inbound call route we have entered my mobile number (from which I call local ObiBT) without + or country code. Does it make any difference ?
Quote
In local GV call history is below and it rings on remote Obi:
00:49:33 From PH1 To PP1(ob510813XXX)
00:49:37 Ringing
00:49:41 Call Connected
00:49:51 Call Ended
I don't think the speed dial you are using is the one I suggested.
It looks like the speed dial you are using is **9510813XXX
The one I suggested is pp(510813XXX*0)
I think this should have failed.
Please change the following:
Remote OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111>(<0:>):ph},{510111111>(<#:>xx.):li},{510111111>(xx.):bt1},{ph}
Now both speed dial formats will work.
QuoteIn remote Obi Call History is below:
01:59:53 From PH1 To PP1(ob510946XXX)
01:59:57 Call Ended (486 Busy Here)
I think this should have worked.
Are you sure this is the call history from the remote OBi?
It looks like this call history is from the local and the above from the remote.
QuoteIn fact Obi Connected phone shows Caller ID with country code and "+" in start while in Inbound call route we have entered my mobile number (from which I call local ObiBT) without + or country code. Does it make any difference ?
Yes, it does make a difference.
Look in the call history.
Whatever the OBi call history shows as callerid, that is what you MUST code in the GV inbound call route.
Quote from: azrobert on January 20, 2015, 04:43:30 PM
Quote
In local GV call history is below and it rings on remote Obi:
00:49:33 From PH1 To PP1(ob510813XXX)
00:49:37 Ringing
00:49:41 Call Connected
00:49:51 Call Ended
I don't think the speed dial you are using is the one I suggested.
It looks like the speed dial you are using is **9510813XXX
The one I suggested is pp(510813XXX*0)
I think this should have failed.
In fact you earlier suggested **9510813xxx for Speed dialing remote Obitalk from local Obi and it works actually. Same sp1(2345640xxx) speed dial for remote GV works which you suggested earlier. But same format doesn't work when I speed dial from remote to local.
Below is local Obi call details:
01:25:17 From PH1 To PP1(ob510813xxx) ** this is local Obi number ,call fails actually.
01:25:44 Call Connected
01:25:54 Call Ended
Call 2 01/22/2015 01:19:14
01:19:14 From PH1 To GT1(2345640xxx) **this is remote GV number. Call connects.
01:19:15 Ringing
01:19:20 Call Ended
Call 3 01/22/2015 01:18:26
01:18:26 From PH1 To PP1(ob510813xxx) **This is remote Obi number. Call connects.
01:18:37 Ringing
01:18:40 Call Connected
01:18:50 Call Ended
Quote from: azrobert on January 20, 2015, 04:43:30 PM
Please change the following:
Remote OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510111111>(<0:>):ph},{510111111>(<#:>xx.):li},{510111111>(xx.):bt1},{ph}
Now both speed dial formats will work.
Still there is no luck, unable to call from Remote to local Obi or GV :(
Call history of remote OBi is below:
02:25:54 Call Ended
Call 2 01/22/2015 02:21:50
02:21:50 From PH1 To PP1(5109946xxx)
Call 3 01/22/2015 02:21:30
02:21:30 From PH1 To PP1(5109946xxx)
Call 4 01/22/2015 02:19:19
02:19:19 From GT1(12347383xxx) To PH1
02:19:19 Ringing
02:19:25 Call Ended
Call 5 01/22/2015 02:18:51
02:18:51 From AA1 To PH1
02:18:51 Ringing
02:18:54 Call Ended
Call 6 01/22/2015 02:18:39
02:18:39 From PP1(510946xxx) To AA1
02:18:39 Ringing
02:18:43 Call Connected
02:18:54 Call Ended
Call 7 01/22/2015 02:17:16
02:17:16 From PH1 To GT1(2347383xxx)
02:17:17 Ringing
02:17:35 Call Ended
Quote from: azrobert on January 20, 2015, 04:43:30 PM
In fact Obi Connected phone shows Caller ID with country code and "+" in start while in Inbound call route we have entered my mobile number (from which I call local ObiBT) without + or country code. Does it make any difference ?
Yes, it does make a difference.
Look in the call history.
Whatever the OBi call history shows as caller ID, that is what you MUST code in the GV inbound call route.
Honestly ObiBT is very unreliable product and phones lose connection frequently. I have tried latest phones like Samsung S4, S5, Lenovo. But on inbound call on local ObiBT doesn't show anything in call history :((
Quote01:25:17 From PH1 To PP1(ob510813xxx) ** this is local Obi number ,call fails actually.
01:25:44 Call Connected
01:25:54 Call Ended
Call 2 01/22/2015 01:19:14
01:19:14 From PH1 To GT1(2345640xxx) **this is remote GV number. Call connects.
01:19:15 Ringing
01:19:20 Call Ended
Call 3 01/22/2015 01:18:26
01:18:26 From PH1 To PP1(ob510813xxx) **This is remote Obi number. Call connects.
01:18:37 Ringing
01:18:40 Call Connected
01:18:50 Call Ended
The above 1st call is from remote to local which fails. Correct?
The 3rd call is from local to remote which succeeds. Correct?
Both are calling the same OBi number.
Is this the problem?
If I don't understand the above call history do following:
Place another call from remote to local.
Post the call history from both the remote and local.
QuoteHonestly ObiBT is very unreliable product and phones lose connection frequently. I have tried latest phones like Samsung S4, S5, Lenovo. But on inbound call on local ObiBT doesn't show anything in call history
If your call history is not showing the inbound BT call then the call is not reaching the OBi200.
You have 2 BT adapters. Correct?
Try using the 2nd adapter.
Maybe the 1st is faulty.
QuoteI tried calling local GV from a mobile phone but it doesn't ring on local Obi.
Is your cell defined on GV as a forwarding number?
Sign into your local GV account.
Click on the Gear Icon.
Click Settings.
Click EDIT under your cell's Forwarding Number.
Click Show Advanced Settings.
Under VoiceMail Access click NO.
Click SAVE.
QuoteStill there is no luck, unable to call from Remote to local Obi or GV
In your local GV account is your Google Chat forwarding number checked?
Call from remote to local, remote Obi Call details:
03:36:44 From PH1 To GT1(2347383xxx)
03:36:45 Ringing
03:36:51 Call Connected
03:37:10 Call Ended
Actually it reached to my mobile via local ObiBT connected ..which is surprising as I didn't change anything in configuration except I changed BT dongle.
Local call details:
Call 1 01/23/2015 02:36:46
02:36:46 From GT1(12345640xxx) To BT1(056789xxxx)
02:36:50 Call Connected
02:37:11 Call Ended
04:00:37 From PH1 To PP1(ob510813xxx)
04:00:40 Call Ended (486 Busy Here)
Above call was using GV Speed dial, and it didn't work with speed dial for Obi to Obi. So far below isn't working:
1- Speed dial from remote Obi to local Obi.
2- Calling remote GV or Obi from local GV or Obi doesn't take me to remote AA anymore (after last configuration advised) and thus I can't chose to proceed with calling ringing on remote Phone or dial out via remote ObiLine or ObiBT.
3- Calling local ObiBT connected mobile from my personal mobile and then connecting with remote AA and having the same route as above in number 2 i.e. dialling our via remote ObiLine/ObiBT or ringing remote phone connected with remote Obi.
Thank you once again :)
Let's do 1 problem at a time starting with #1.
I'm trying to keep Reply#27 configuration up to date with any changes.
This is what you should have:
Local OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510222222>(xx.):bt1},{ph}
In the remote OBi don't use a speed dial defined as **9510111111
Use pp(510111111)
When you use **9510111111 the number is routed to the Phone Port Digitmap, the Phone Port OutboundCallRoute and then to the OBiTalk network.
This should work, but something is causing a problem.
When you defined the speed dial as pp(510111111) the call goes directly to the OBiTalk network.
Try the call again.
Post the call history from both the local and remote OBi200s.
I found a typo.
This is what you have now:
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#):aa)},{ph}
Change it to:
{(Local_GV#):aa},{ph}
This should fix calling the remote GV# with the local GV# and getting the AA.
You don't get the AA when calling from the local phone port.
You get the AA when you call BT with your mobile.
I changed some text in reply#27 like this:
From local phone port dial:
0 Ring remote phone
#8005551212 Remote Line call
8005551212 Remote BT call
18005551212 Local SP1 call
From AA after calling BT with your mobile:
Reply 1 to ring remote phone
Otherwise reply 2 then dial:
#8005551212# Remote Line call
8005551212# Remote BT call
18005551212# Local SP1 call
QuoteYet another issue is that when from my mobile phone I call local ObiBT it rings on phone connected with local Obi and doesn't connect me with remote Obi AA. In fact Obi Connected phone shows Caller ID with country code and "+" in start while in Inbound call route we have entered my mobile number (from which I call local ObiBT) without + or country code. Does it make any difference ?
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{+ccmmmmmm:aa},{ph}
Change cc to the country code
Change mmmmmm to your mobile's CID
+ccmmmmmm must match what you see in the OBi call history.
Edit:
This is what happens when you call local BT from your mobile.
You are connected to the LOCAL AA.
The Local AA sends the dialed number to the remote OBi200, in the same format as if it was dialed from the local phone port.
I tried this but there is no incoming call on local ObiBT and therefore it doesn't show any call either on call history of local or remote Obi device.
I have tried all possible Caller ID formats without country code, with country code , with 00 and with a "+".
This is strange as GV calls from remote Obi now goes to my mobile via local Obi/ObiBT connected mobile.
So currently I am not able to reach remote AA either using my mobile or cordless connected with local Obi.
**I am planning to use ObiLine with remote OBi instead as Bluetooth isn't a reliable solution. I will connect a fixed wireless terminal (which uses a SIM card and produces dial tone to use it like a normal PSTN line). SO in this case can I have your help to configure remote Obi AA to allow me to call using ObiLIne or to call phone connected with phone port of remote Obi ? I mean calling my family for free or calling out using ObiLine as and when required.
In this VoIP censored area (specially in office) this will be a great scenario where GV works at home (local Obi) and I can call cell phone connected with local Obi and reach remote AA and dial to my family or use remote ObiLIne. Currently calls from remote Obi are reaching my mobile which is great but I can't dial out from my cell phone.
Happy weekend :)
QuoteI tried this but there is no incoming call on local ObiBT and therefore it doesn't show any call either on call history of local or remote Obi device.
This is strange as GV calls from remote Obi now goes to my mobile via local Obi/ObiBT connected mobile.
If I understand you correctly outbound BT calls work, but inbound don't.
This is strange.
For a test try this:
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{aa}
Now any inbound call will go to the AA.
Please report back what happens.
If it works, you will be able to see the callerid in the call history.
--------------------------------------------------------------------------------
QuoteSo currently I am not able to reach remote AA either using my mobile or cordless connected with local Obi.
Outbound calls from the local phone port don't go to the AA.
Dial 0 from the local phone port.
Does it ring the remote phone port?
----------------------------------- ------------------------------------------
We have so many route combinations defined, I'm confused on how the OBiLine is going to be used.
Currently the remote OBiLine is used for remote outbound calls.
Do you want to change this to receive inbound calls from your local mobile?
Will the OBiLine be located at the remote site, but have a local number?
or
Is this a 2nd OBiLine and will be located at the local site?
----------------------------------------------------------------------------
QuoteCurrently calls from remote Obi are reaching my mobile which is great but I can't dial out from my cell phone.
Are these the calls coming from the remote BT?
If yes, then inbound BT calls work at the remote site, but not at the local site.
There must be some coding error at the local site.
Hopefully my 1st suggestion above will work.
-------------------------------------------------------------------------------
Can you call the remote GV number from your mobile?
You can reach the remote AA this way.
If this is a toll call do the following:
Install the Hangouts app on your local mobile.
Android has a 2nd app (Hangouts Dialer).
Hangouts will allow you to use GV for outbound calls from your mobile.
Configure it with your local GV number.
Now call the remote GV number with Hangouts from your mobile to be routed to the AA.
Another Option is to install the Obion app on your mobile then you can communicate directly with the remote OBi200 over the OBiTalk network. Some people have problems using the Obion app.
Quote
If I understand you correctly outbound BT calls work, but inbound don't.
This is strange.
For a test try this:
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{aa}
Now any inbound call will go to the AA.
Please report back what happens.
If it works, you will be able to see the callerid in the call history.
I tried but no success. In fact I have noticed one thing is that when I call connected phone green phone light on Obi device turns off and after a few rings even power light turns off...looks like Obi device goes through power cycle?
Quote
Outbound calls from the local phone port don't go to the AA.
Dial 0 from the local phone port.
Does it ring the remote phone port?
Actually I hear GV message that your call couldn't be completed.
Quote
We have so many route combinations defined, I'm confused on how the OBiLine is going to be used.
Currently the remote OBiLine is used for remote outbound calls.
Do you want to change this to receive inbound calls from your local mobile?
Will the OBiLine be located at the remote site, but have a local number?
or
Is this a 2nd OBiLine and will be located at the local site?
I have attached a graphical image to explain this. I want to use remote PSTN line while sitting in another country and want to transfer all calls on remote PSTN to reach my mobile travelling via Obi+attached bluetooth phone.
Quote
Can you call the remote GV number from your mobile?
You can reach the remote AA this way.
If this is a toll call do the following:
Install the Hangouts app on your local mobile.
Android has a 2nd app (Hangouts Dialer).
Hangouts will allow you to use GV for outbound calls from your mobile.
Configure it with your local GV number.
Now call the remote GV number with Hangouts from your mobile to be routed to the AA.
I called from my mobile and it rings on attached remote phone.
QuoteActually I hear GV message that your call couldn't be completed.
Please check the local phone port outbound call route and DigitMap. Only 10 digit number prefixed with "1" should be routed to GV. Everything else should be routed to the remote OBi200.
I added "***" to the DigitMap for the AA2. Nothing to do with this problem, just previously missed it.
Local OBi:
Physical Interfaces -> Phone Port
DigitMap:
(***|1xxxxxxxxxx|@@.S2)
OutboundCallRoute:
{***:aa2},{(1xxxxxxxxxx):sp1},{(<510222222*>@@.):pp}
Dial 0 from the local phone port and post the call history.
------------------------------------------------------------------------
QuoteI called from my mobile and it rings on attached remote phone.
Add your mobile number to the inbound rule.
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#|your_mobile#):aa},{ph}
I added OBion app as another solution to my previous post after you quoted me.
---------------------------------------------------------------------------
I'm still not sure I understand. You want all inbound calls on the remote OBiline to be forwarded to your mobile via remote BT. Correct? This is a new requirement, not a fix to circumvent one of the other problems. Correct?
Remote OBi:
Physical Interfaces -> Line Port -> InboundCallRoute:
bt1(your_mobile#)
QuotePlease check the local phone port outbound call route and DigitMap. Only 10 digit number prefixed with "1" should be routed to GV. Everything else should be routed to the remote OBi200.
I added "***" to the DigitMap for the AA2. Nothing to do with this problem, just previously missed it.
Local OBi:
Physical Interfaces -> Phone Port
DigitMap:
(***|1xxxxxxxxxx|@@.S2)
OutboundCallRoute:
{***:aa2},{(1xxxxxxxxxx):sp1},{(<510222222*>@@.):pp}
Dial 0 from the local phone port and post the call history.
I tried and hear message "Number you dialled has been rejected by service provider, reason being 404"
Quote
Add your mobile number to the inbound rule.
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#|your_mobile#):aa},{ph}
I added OBion app as another solution to my previous post after you quoted me.
In fact I don't want calls directly on remote GV to transfer to my mobile but in facct any call on remote ObiLINE + Local GV+ Local Obi to be transfered to my mobile.
I tried to explain it in the image, I can elaborate it more if you like :) In fact purpose of all is to use remote PSTN line remotely and transfer all calls on that remote PSTN to my local mobile (which isn't connected directly with Obi) via local ObiBT (which is connected with a dedicated mobile phone).
In fact if I call local ObiBT phone and manage to reach remote AA (which gives me options to chose either calling remote GV and ring on phone or use remote PSNT line) will be awsome and is what I want.
My fault, I didn't take a close look at your diagram. You want inbound calls on the remote OBiLine sent to your personal mobile. This is the same function you have on the remote BT and the code is the same.
Remote OBi:
Physiscal Interfaces-> Line port -> InboundCallRoute:
pp(510111111*Your_Cell#)
_______________________________________________________
The local phone port is not functioning properly.
Please dial 0 again and post the call history from both the local and remote OBi200s.
_______________________________________________________
You can't reach the AA from your personal mobile by calling the local BT.
The call history doesn't show any activity, indicating the call is not reaching the local OBi.
You said:
QuoteI tried but no success. In fact I have noticed one thing is that when I call connected phone green phone light on Obi device turns off and after a few rings even power light turns off...looks like Obi device goes through power cycle?
This suggests a hardware problem.
I made a suggestion to circumvent the above problem by calling the remote GV# directly with your mobile or using the hangouts app. You tried it before I made any changes and said it rang the phone port. The following will send the call to the AA.
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#|your_mobile#):aa},{ph}
I will give it a try today and will report. But I think we are missing something here, I think I haven't explained it well :(
I am writing you after a few days sickness :) Trying to achieve it again, you definitely have been a great support indeed :)
In remote line setting I have entered inbound call route as pp(510946xxx*056789xxxx) as I understood it, where 510946xxx is local Obitalk number and is my personal mobile that I carry (not the one connected with local Obi with Bluetooth). Do you think call on remote ObiLine route to local Obi and then to mobile via connected Bluetooth mobile ? I think even in local Obitalk there must be setting to route this call via Bluetooth..what do you say?
I was earlier able to reach remote Obi AA dialing from local phone port, I am forgetting which setting that you recommended earlier. But there is no way I can reach remote AA calling local ObiBT and reaching remote AA and then using remote PSTN line?
I have ordered another Obi200 device which will arrive in a week just to see if existing local Obi is faulty. Also as I have ObiLine as well locally and remotely I am considering using GSM Wireless terminal to give dial tone to ObiLine and not to use bluetooth (considering there might be some issue with it?).
Local OBi Number: 510946xxx
Remote OBi Number: 510813xxx
Personal Mobile#: 056789xxxx
Local OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510813xxx>(xx.):bt1},{ph}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{+cc056789xxxx:aa},{ph}
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(1xxxxxxxxxx):sp1},{(<510813xxx*>@@.):pp}
Physical Interfaces -> Phone Port
DigitMap
(***|1xxxxxxxxxx|@@.S2)
OutboundCallRoute
{999:aa},{***:aa2},{(1xxxxxxxxxx):sp1},{(<510813xxx*>@@.):pp}
Speed dials:
pp(510813xxx*0) Ring phone
pp(510813xxx*#8005551212) Line call
pp(510813xxx*8005551212) BT call
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(1Local_GV#):aa},{ph}
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510946xxx >(<0:>):ph},{510946xxx>(<#:>xx.):li},{510946xxx>(xx.):bt1},{ph}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
pp(510946xxx*056789xxxx)
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(<0:>):ph},{(<#:>xx.):li},{bt1}
Physiscal Interfaces-> Line port -> InboundCallRoute:
pp(510946xxx*056789xxxx)
From local phone port dial:
999 Local AA
0 Ring remote phone
#8005551212 Remote Line call
8005551212 Remote BT call
18005551212 Local SP1 call
From AA after calling BT with your mobile:
Reply 1 to ring remote phone
Otherwise reply 2 then dial:
#8005551212# Remote Line call
8005551212# Remote BT call
18005551212# Local SP1 call
I created the above configuration from a copy of reply#27 and updated it with the OBi numbers of the OBi202s and your mobile number. You were having problems, so I recommended in Reply#29 using GV to reach the AA. I don't know if you are using any of this code, so I didn't include it in the above configuration.
______________________________________
QuoteI think even in local Obitalk there must be setting to route this call via Bluetooth..what do you say?
Remote OBi:
Physiscal Interfaces-> Line port -> InboundCallRoute:
pp(510946xxx*056789xxxx)
The above code will route inbound line calls to the local OBi with your mobile number included.
Local OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510813xxx>(xx.):bt1},{ph}
The above code will route ANY call from the remote OBi with an attached number out BT.
The remote BT inbound calls use the same code, so if BT calls work then there is probably something wrong with the OBiLine adapter.
______________________________________
QuoteI was earlier able to reach remote Obi AA dialing from local phone port, I am forgetting which setting that you recommended earlier.
Local OBi:
OutboundCallRoute
{999:aa},{***:aa2},{(1xxxxxxxxxx):sp1},{(<510813xxx*>@@.):pp}
I added dialing "999" to route to the local AA then the local AA will route the call to the remote OBi.
______________________________________
QuoteBut there is no way I can reach remote AA calling local ObiBT and reaching remote AA and then using remote PSTN line?
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{+cc056789xxxx:aa},{ph}
The above rule will route local inbound BT calls from your mobile to the local AA. I believe you previously said the call history showed the callerid had a plus sign and the country code. The callerid in the above rule must exactly match the callerid in the call history.
If you still can't get the call to be routed to the local AA, you can unconditionally route all inbound BT call to the AA with the following rule:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute: aa
I have already settings which you mentioned in post#29.
Below setting in remote Obi actually rings phone attached to remote Obi and doesn't connect me with remote AA.
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#):aa},{ph}
*My Local GV in above number is without + or 1 in the start.
------------------
In post 29 you have mentioned:
"You can have both methods setup at the same time.
Leave the BT Inbound route unchanged like this.
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):aa)},{ph,ph2}"
Shoudl this be in local or remote Obi ? And number "1?4808370001" is local or remote GV? Should it be withour "1?"
--------------------------
You have mentioned:
Local OBi:
OutboundCallRoute
{999:aa},{***:aa2},{(1xxxxxxxxxx):sp1},{(<510813xxx*>@@.):pp}
I added dialing "999" to route to the local AA then the local AA will route the call to the remote OBi. "
Where should this go? In GV route or AA?.
-------------------
So far the issue is that on local Obi there is no inbound call when I call local ObiBT attached phone.
I will give it another try and will report back. Thank you :)
QuoteBelow setting in remote Obi actually rings phone attached to remote Obi and doesn't connect me with remote AA.
Voice Services -> SP1 Service -> InboundCallRoute:
{(Local_GV#):aa},{ph}
Remote OBi:
CallerID on an inbound GV trunk has the "1" prefix.
Try:
{(1Local_GV#):aa},{ph}
______________________________________
QuoteIn post 29 you have mentioned:
"You can have both methods setup at the same time.
Leave the BT Inbound route unchanged like this.
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{(1?4808370001):aa)},{ph,ph2}"
Shoudl this be in local or remote Obi ? And number "1?4808370001" is local or remote GV? Should it be withour "1?"
I believe this was for the remote OBi, and don't know why I suggested it. I probably didn't understand your requirements. Ignore this.
______________________________________
QuoteYou have mentioned:
Local OBi:
OutboundCallRoute
{999:aa},{***:aa2},{(1xxxxxxxxxx):sp1},{(<510813xxx*>@@.):pp}
I added dialing "999" to route to the local AA then the local AA will route the call to the remote OBi. "
Where should this go? In GV route or AA?.
This is a replacement for the local Phone Port OutboundCallroute.
I am really confuse here to be honest. Here are issue which I am still facing:
1- All dialed calls from local phone are reaching remote Obi Phone even if I am dialing any other GV number.
2- I am not able to reach remote AA to use either remote PSTN line o paired Bluetooth phone.
3- Calls on remote PSTN aren't reaching local Obi and then to my phone via paired mobile.
I think I am still not explained it well ? Can you please see the diagram.
Thank you :)
*P.S. If I call remote GV from Hangout dialer it hangs up after mentioning a brief message with +cc234567..
I wast reading your another post in forum and was wondering if rules can be defined for:
-All calls from local ph starting with 02, 03, 04, 05, 06, 07, 08,09 going through remote PSTN and/or ObiBT.
- All calls starting with any other number (except 510 going through OBi) going through GV.
This isn't a new requirement, in fact I came to this after reading your post.
With this post I'm only going to address calls dialed from the local phone.
Quote1- All dialed calls from local phone are reaching remote Obi Phone even if I am dialing any other GV number.
All dialed numbers in the format 1xxxxxxxxxx should be routed out the local SP1 (GV), all other numbers should be routed to the remote OBi.
Are you saying this is not working?
Quote-All calls from local ph starting with 02, 03, 04, 05, 06, 07, 08,09 going through remote PSTN and/or ObiBT.
- All calls starting with any other number (except 510 going through OBi) going through GV.
The following is the outbound routing for calls sent to the remote OBi:
Currently, any number with a prefix of # (pound sign) will be routed out PSTN.
All other numbers will be routed out BT.
Are you saying this is not working? Are these calls ringing the phone attached to the remote OBi?
Is the following what you want?
Numbers dialed from local OBi phone starting with 02 thru 09 routed to the remote OBi.
Then what do you want? Should they be routed out the remote PSTN or BT?
All other numbers except 510 routed out the LOCAL SP1 (GV).
What is a 510 number and where should they be routed?
Is this a number or prefix?
Is this an OBi number?
Quote
With this post I'm only going to address calls dialed from the local phone.
1- All dialed calls from local phone are reaching remote Obi Phone even if I am dialing any other GV number.
All dialed numbers in the format 1xxxxxxxxxx should be routed out the local SP1 (GV), all other numbers should be routed to the remote OBi.
Are you saying this is not working?
Actually if I try to dial any GV number in standard format is ringing remote GV. I have set "4" as speed dial for remote GV though and 3 for remote Obi but any number I dial and it is ringing remote GV.
Quote
Quote
-All calls from local ph starting with 02, 03, 04, 05, 06, 07, 08,09 going through remote PSTN.
- All calls starting with any other number (except 510 going through OBi) going through GV.
The following is the outbound routing for calls sent to the remote OBi:
Currently, any number with a prefix of # (pound sign) will be routed out PSTN.
All other numbers will be routed out BT.
Are you saying this is not working? Are these calls ringing the phone attached to the remote OBi?
So I should dial any number will prefix # to use remote PSTN ? I will give it a try and will post as it is night at remote site and I fear it will ring remote phone to wake everyone up. But earlier I followed your post#27 and now when I dial 999 AA respond, I am not sure if it is remote or local AA. It gives me three options but calls still ring at remote Obi phone.
Quote
Is the following what you want?
Numbers dialed from local OBi phone starting with 02 thru 09 routed to the remote OBi.
Then what do you want? Should they be routed out the remote PSTN or BT?
Yes exactly, in fact this summarizes my dialling out requirement, these numbers range routed through remote PSTN or BT. I have both BT and PSTN options available as I have ObiBT and ObiLine. But Bluetooth will be quick to setup for now as I have ordered a fixed GSM terminal generating dial tone which I will plug into ObiLINE later to make it more reliable. Can we make dial out using Bluetooth now and change to PSTN later ?
Quote
All other numbers except 510 routed out the LOCAL SP1 (GV).
What is a 510 number and where should they be routed?
Is this a number or prefix?
Is this an OBi number?
Yes all other calls to be routed via SP1 starting with 001 lets say.
510 is prefix for ObiTalk, I believe that is only prefix for Obitalk ?
Local OBi Number: 510946xxx
Remote OBi Number: 510813xxx
Personal Mobile#: 056789xxxx
Local OBi:
Voice Services -> OBiTalk Service -> InboundCallRoute:
{510813xxx>(xx.):bt1},{ph}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
{+cc056789xxxx:aa},{ph}
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(<510813xxx*>(0[2-9]xx.|0)):pp},{sp1}
Physical Interfaces -> Phone Port
DigitMap
(***|1xxxxxxxxxx|@@.S2)
OutboundCallRoute
{999:aa},{***:aa2},{(<510813xxx*>(0[2-9]xx.|0)):pp},{sp1}
Speed dials:
pp(510813xxx*0) Ring Remote phone
pp(510813xxx*02123456789) BT/Line call
sp1(anything) SP1 call
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(1Local_GV#):aa},{ph}
Voice Services -> OBiTalk Service -> InboundCallRoute:
Route 02 thru 09 numbers to BT
{>(<0:>):ph},{bt1}
Route 02 thru 09 numbers to Line
{>(<0:>):ph},{li}
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
pp(510946xxx*056789xxxx)
Voice Services -> Auto Attendant -> DigitMap:
(x|[1-9]x|@@.S2)
Voice Services -> Auto Attendant -> OutboundCallRoute:
Route 02 thru 09 numbers to BT
{0:ph},{(0[2-9]xx.):bt},{sp1}
Route 02 thru 09 numbers to Line
{0:ph},{(0[2-9]xx.):li},{sp1}
Physiscal Interfaces-> Line port -> InboundCallRoute:
pp(510946xxx*056789xxxx)
From local phone port dial:
999 Local AA
0 Ring remote phone
02123456789 Remote BT/Line call
Anything (except 02 thru 09) Local SP1 call
From AA after calling BT with your mobile:
Reply 1 to ring remote phone
Otherwise reply 2 then dial:
02123456789 Remote BT/Line call
Anything (except 02 thru 09) Local SP1 call
From AA after calling remote GV from Local GV:
Reply 1 to ring remote phone
Otherwise reply 2 then dial:
02123456789 Remote BT/Line call
Anything (except 02 thru 09) Remote SP1 call
Reply#55 is the current configuration.
Ignore all others.
The items in BOLD are changes from the config in Reply#48.
In the Remote OBi I gave you 2 options to route to BT or Line.
See the end of the post for the dialing rules.
When you dial 999 you are sent to the Local AA.
After you reply, the Local AA will send the correct dialed numbers to the Remote OBi.
It was easier to do it this way instead of sending 999 to the Remote AA because this was already setup for calls from your mobile.
Why do you want this function from the Local Phone when you can just dial the number without the AA?
You need the AA when you call in from your mobile, but not from the phone port.
Quote from: azrobert on February 17, 2015, 03:53:17 PM
Reply#55 is the current configuration.
Ignore all others.
The items in BOLD are changes from the config in Reply#48.
In the Remote OBi I gave you 2 options to route to BT or Line.
See the end of the post for the dialing rules.
When you dial 999 you are sent to the Local AA.
After you reply, the Local AA will send the correct dialed numbers to the Remote OBi.
It was easier to do it this way instead of sending 999 to the Remote AA because this was already setup for calls from your mobile.
Why do you want this function from the Local Phone when you can just dial the number without the AA?
You need the AA when you call in from your mobile, but not from the phone port.
Amazing ;D Thank you very much. It worked indeed i.e. I could use remote Mobile connected with remote Obi ..dialing out this way.
Three issues1st issue is that call on remote connected cell isn't reaching local mobile. Also if I call local mobile connected with local Obi from my personal mobile isn't reaching local AA and it keeps on ringing.
2nd issue is that sometime both sides (GV-GV) can't hear each other. Earlier there was no such issue.
3rd issue is that Obi-Obi isn't working anymore. Instead GV speaks up that number can't be dialed.
I am thinking I should use ObiLine instead as ObiBT probably works for dialing out only and doesn't respond to calls directly on mobile which is connected to Obi. Do you think it will help? Another solution with ObiLine I am thinking about is CobraPhoneLink http://www.cobraphonelynx.com/ (http://www.cobraphonelynx.com/), any advice on it?
I will connect PSTN line with ObiLine and will give it a try, will give my feedback today.
Quote3rd issue is that Obi-Obi isn't working anymore. Instead GV speaks up that number can't be dialed.
My fault. I forgot to include dialing zero in the new configuration to ring the remote phone port.
Local OBi:
Voice Services -> Auto Attendant -> OutboundCallRoute:
{(<510813xxx*>(0[2-9]xx.|0)):pp},{sp1}
Physical Interfaces -> Phone Port
OutboundCallRoute
{999:aa},{***:aa2},{(<510813xxx*>(0[2-9]xx.|0)):pp},{sp1}
Quote2nd issue is that sometime both sides (GV-GV) can't hear each other. Earlier there was no such issue.
This was a reported GV problem. I was experiencing the same problem, but it was fixed awhile ago. I can't help if you are still having the problem.
Quoteif I call local mobile connected with local Obi from my personal mobile isn't reaching local AA and it keeps on ringing.
Temporarily make the following change:
Local OBi:
Voice Services -> OBiBlueTooth1 -> InboundCallRoute:
ph
This is to make sure there isn't a syntax error in the BT inbound route code.
Call the cell attached to BT.
Does the local phone port ring?
If it doesn't, the call isn't getting to the OBi and I can't help you.
Quote1st issue is that call on remote connected cell isn't reaching local mobile.
Not sure I understand. Is this calling the remote cell connected to BT and having the call routed to your personal cell via local BT?
Wasn't this working? Check the local call history to see if the call is routed out local BT.
Hi Azrobert,
I hope you are doing well :)
I had an accident and returning to this forum after some time.
I tried above but it didn't work so I gave up BT idea and plugged in the ObiLine instead with remote Obi200. Basically ObiLine is getting PSTN line from a GSM Fixed Wireless Terminal that generates a dial tone from a SIM card inserted and you can plug in a PSTN phone into it to dial out.
So basically through this Vodafone device I am getting dial tone and have plugged it into ObiLine. I have done configuration you suggested to either use BT or Obiline changing it to ObiLine only.
Below is what I see when I dial 999 and chose 2 and then the desired number below is what I get:
11:16:57 From AA1 To PP1(510813xxx*032xxxxxxxx)
11:17:02 Call Ended (503 Service Unavailable)
Also incoming calls on that PSTN line (calling it PSTN as it generates tone but from GSM) are also not reaching locally.
I hope you are OK.
When I didn't hear from you after my last post, I thought everything was working.
No such luck. LOL.
Anyway, I disconnected my PSTN line from my OBi110 and then routed a call to it from my OBi200. I received the same 503 error and also got an IVR message "All Circuits are Busy". I suspect there is something wrong with your PSTN line. I can't help you with hardware problems.
Make sure you are at the current firmware level. There has been some recent fixes for OBiLine. I think these are for an echo problem so I don't think it will help, but it can't hurt to be at the current FW level.
You should be able to just dial the number without using the Auto Attendant. This will not fix your problem.
Azrobert,
I hope you are doing well.
Because of your great help I have been able to talk to my family and friends so peacefully when they call me from my home country and it reaches to my mobile, thanks a million :)
I need some help if you can spare time responding. I want to know that my current configuration is as per your post #55 in this thread, I use phone attached to local Obihai device to use remote GSM line paired with remote Obihai.
Is there any way I can use Hangout Dialer on my mobile phone to call remote GV on remote Obihai (which is bluetooth paired with a GSM phone) and when remote Obihai reads my local GV number my it gives me access to use remote GSM and then dial out just like now ?
Your help is appreciated like always.
Route the Hangouts CallerID to the Auto Attendant.
Remote OBi:
Voice Services -> SP1 Service -> InboundCallRoute:
{(1Local_GV#|1Hangouts#):aa},{ph}
I gave you 2 options for the Auto Attendant OutboundCallRoute. If you are already routing calls to BT then the above is all you need.
I updated Reply#55.
Thank you for your reply.
Is {(1Local_GV#|1Hangouts#):aa},{ph} considering that local GV and Hangout accounts are different ? I am currently using same number for both local Obi and hangout dialer.