(2) Obi 202's in one place: Distinctive ring and other questions
Chuck_in_ABQ:
I have set up the following:
Obi-1 (202):
SP1=home (GV) (ring house phone) (**1 or default)
SP2=Dad (GV) (ring house phone) (**2)
SP3=Mom (GV) (ring house phone plus obitalk on tablet) (**3)
SP4=Anveo free SIP (for 911) (911 and 933)
Ph has handset (all house phones)
Ph2 has fax machine (have not tested)
Obi-2
SP1=Kid1 (GV) (ring obitalk only) (**6)
SP2=Kid2 (GV) (ring house and tablet) (**7)
SP3=Kid3 (GV) (ring tablet only) (**8)
- Any user can call out from the house phone on their own account by preceding with the **n code.
- Distinctive ringtones are used on lines 1 through 4. Lines 6-8 come in on obitalk connection, and all have the same ringtone. This is ok since only one kid wants the house phone to ring. I was unable to find any way to get distinctive ringtones for all users on the second Obi for the phone connected to obi-1. Setting distinctive rings on obi-2 spn did not change the ring that arrived on ph1 of obi-1. The ring that arrived was set by the obitalk settings on obi1.
- When a user connects to their gateway with Obitalk app on tablet, their correct default trunk is used, such that for example, when Mom connects to Obi1, her default outgoing calls are on sp3. She does not have to dial **3 to present her callerID to friends.
- Press #, or *, or 123 on home phone to get voicemail (call own number at GV). Can call **n#, **n*, or **n123 to get other voice mails
-On tablets, same to get to VM except # and **n# does not work
- I have made the following setups:
Obi-1 = 5008yyyyy
Obi-2 = 5002yyyyy
Mom & Dad’s obitalk gateways are set to 5008yyyyy
All kid’s obitalk gateways are set to 5002yyyyy
Both Obi’s
User maps:
Ste = (<311:15057682000>|<411:18003733411>|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1505>[2-9]xxxxxx|011xx.)
Cot = (2908yyyyy|2902yyyyy|2903yyyyy|2907yyyyy|29035yyyy|5002yyyyy)
Kid1 = (2903yyyyy)
Kid2 = (2907yyyyy)
Kid3 = (2902yyyyy)
Mom = (2908yyyyy)
Dad = (29035yyyy)
Out = ((Mste)|#|*|123)
Obi-1:
ITSP Profile N General;
DigitMap = ((Mste)|<[#*]:1505yyyyyyy>|<123:1505yyyyyyy>) where yyyyyyy is the Google Voice phone number for the person assigned to that channel
ITSP Profile D General
DigitMap = (911|933) for 911 and testing ONLY
Phone1
DigitMap = ([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911S0|933S0|**0|***|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|**3{t=di2} (Msp3)|**[6-8]{t=di2}(Mout)|**9{t=di2}(Mpp)|(Msp1))
OutboundCallRoute = {911:sp4},{933:sp4},{([1-9]x?*@@.):pp},{(**[6-8](Mout)):pp(ob500225223$2)},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp}, {(Msp1):sp1}
Duplicated for phone2
SP1, InboundCallRoute = {ph1,ph2,pp(ob2908yyyyy)} (calls Mom’s tablet, fax, and house phone)
SP2, InboundCallRoute = {ph1}
SP3, InboundCallRoute = {ph1,pp(ob2908yyyyy)} (Calls Mom’s tablet and house phone)
SP2, InboundCallRoute = {ph4}
Obitalk Service
DigitMap (unchanged) = (<ob>xxxxxxxxx|obxxxxxxxxx)
InboundCallRoute = {(Mcot)>(911): sp4}, {(Mcot)>(933): sp4},{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Msp3)),(Mcot)>(<**3:>(Msp3)):sp3},{(Mcot)>(<*4:>(Msp4)),(Mcot)>(<**4:>(Msp4)):sp4},{(Mcot)>(*[6-8](Mout)),(Mcot)>(**[6-8](Mout)):pp(ob500225223$2)},{(Mmom)>(<:>(Msp3)):sp3},{(Mdad)>(<:>(Msp2)):sp2},{(Mcot)>(<:>(Msp1)):sp1},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},{(Mcot)>(Mpli):sp1},{(Mcot)>(Mpli):sp1},{(Mcot):aa},{ph} (If star codes are included, route as asked. If not, route based on user. Otherwise route to sp1. 911 and 933 routed to Anveo)
Similar things need to be done on AA, but I have not set that up yet…
Obi2:
ITSP Profile N General;
DigitMap = ((Mste)|<[#*]:1505yyyyyyy>|<123:1505yyyyyyy>) where yyyyyyy is the Google Voice phone number for the person assigned to that channel, same as Obi1
Phone1 and Phone 2 not set up, no handsets connected
SP1, InboundCallRoute = {pp(ob2903yyyyy)} (Routes to Kid 1 tablet only)
SP2, InboundCallRoute = {pp(ob5008yyyyy),pp(ob2907yyyyy)} (Routes to Kid 2 tablet and house phone on obi-1)
SP3, InboundCallRoute = {pp(ob2902yyyyy)} (Routes to Kid 3 tablet only)
Obitalk service:
Digitmap (unchanged) = (<ob>xxxxxxxxx|obxxxxxxxxx)
Inbound Call Route = {(Mcot)>(911): pp(ob5008yyyyy$2)}, {(Mcot)>(933): pp(ob5008yyyyy$2)},{(Mcot)>(<*6:>(Msp1)),(Mcot)>(<**6:>(Msp1)):sp1},{(Mcot)>(<*7:>(Msp2)),(Mcot)>(<**7:>(Msp2)):sp2},{(Mcot)>(<*8:>(Msp3)),(Mcot)>(<**8:>(Msp3)):sp3},{(Mcot)>(*[1-3](Mout)),(Mcot)>(**[1-3](Mout)):pp(ob5008yyyyy$2)}, {(Mkid1)>(<:>(Msp1)): sp1} ,{(Mkid2)>(<:>(Msp2)): sp2 ,{(Mkid3)>(<:>(Msp3)): sp3},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},{(Mcot)>(Msp1):sp1},{(Mcot):aa},{ph}
SO, this MOSTLY works. I do have one issue, though. If I try to call voicemail, from a tablet connected to one obi (say, kid-1), and call to a voicemail on the other Obi, it fails (using say, **2123 to get to Dad’s voicemail). If Kid-1 dials **6123, **7123, **8123, or 123, he gets connected to the appropriate VM. However, cross-connecting the two obi’s to VM fails. However, from the house handset, we can dial **n# or **n123 where n is [1,2,3,6,7,8] and all works just fine! On Kid-1’s tablet, I even tried to call **21505yyyyy where yyyyy was Dad’s Google voice number, such that the only thing that has to happen is strip off the **2 (or *2 by the time it gets to Obi1)
The call history has limited information. Here are several attempts:
First call, I dialed **2123 on the tablet. On Obi2, the log shows:
12:56:07 From 'Dan' PP1(2903yyyyy; GW=2903yyyyy) To PP1(*2123; GW=5008yyyyy)
12:56:08 Ringing
12:56:08 Call Connected
12:56:09 Call Ended
On Obi1, the call routed to the AA (not sure why it did not resolve):
12:56:09 From 'Dan' PP1(2903yyyyy; GW=2903yyyyy) To AA1
12:56:09 Ringing
12:56:13 Call Connected
12:56:20 Call Ended
Second call, I dialed **2yyyyyyy where yyyyyyy is the 7-digit local phone number. On Obi2, it fully resolved the local phone number to a 10-digit number before passing it on:
12:56:30 From 'Dan' PP1(2903yyyyy; GW=2903yyyyy) To PP1(*21505yyyyyyy; GW=5008yyyyy)
12:56:31 Ringing
12:56:31 Call Connected
12:56:32 Call Ended
But on OBI-1, the phone call got “lost”. The device showed connected, but I do not know what it was connected to. Never got any response form Google Voice, just a dead line. The “target transfer” is probably part of the problem:
12:56:30 From 'Dan' PP1(2903yyyyy; GW=5002yyyyy) To GT2(1505yyyyyyy)
12:56:30 Ringing
12:56:31 Call Connected
12:56:32 New Peer: 'Dan' PP1(2903yyyyyyy; GW=2903yyyyyyy) Transfer Target
12:56:48 Call Ended
Third call I dialed **21505yyyyyyy, so that the only thing that has to happen is stripping of the *2. This resulted the same as call 2. It is apparently routing to the correct GT channel (#2). But, then something happens. Strange thing, if I dial **2zzzzzzz where zzzzzzz is any other number other than the GV number for channel 2, the call appears to go through (with a transfer target)!
Not sure what is going wrong when this setup calls GV rather than some other number (even if the other number is a GV number, just not the one that will dump right into VM).
Other than this, and the lack of distinctive ringing on Ph1 of Obi-1 when the call comes in on obi2, I am pleased with the setup.
Have not tested 933 from tablet connected to obi-2 yet…
RFord:
Chuck: I must admit that I have not read your post in detail, so I might have missed something. How are you handling E911 on OBi_2? I would think that in case of an emergency, the kids should be able access E911 from OBi_2. If this is already addressed, please ignore my comments.
Maybe you can do some form of IP-Dialing (I don't know how you can do this with OBi ATA) and have all E911 outgoing calls from OBi_2 be done through OBi_1. The other option would be to set-up a Sub-account at Anveo under your Main Account and setup that Sub-Account on SP4 on OBi_2. Please check to make sure that the E911 for the Sub-Account will utilize the E911 information of the Main Anveo account to avoid paying two separate E911 charges.
Chuck_in_ABQ:
The biggest issue with 911 through the tablets would be that they use those when out (wherever there is WiFi), and thus the location information is wrong.
If you look at the routing on the Obi-2 obitalk, the first two items take care of 911/933. Still need to test, but it should go on over to the sp4 on obi1.
Chuck
Chuck_in_ABQ:
Well, almost right. All the outgoing calls are correct.
However, incoming calls on obi#2, line SP2, which get routed to obi#1 to ring in the house, actually end up going to aa. I had not put in the aa statement (next to last on obitalk incoming routing on obi#1) while working things out, but added it back in. It seems that the calls coming in on obi-2, forwarding to obi#1, are falling through to aa. Since obi-2 is in the COT, and the call has not matched any of the outgoing patterns, it must be trapped by the aa.
For now I removed the aa statement, so instead things fall through to the phone.
Any ideas how to get incoming calls from obi-2 to go to phone, but still have capability of aa? For now, I really don't need aa, so I'll keep it off, but I feel as though I am missing a step here. Maybe I should just remove the obi-2 from the COT?
Oh well, it works without aa
Chuck
ianobi:
It does seem that the only time OBi#2's number is used in cot is incoming calls on obi#2, line SP2. However, I guess you might use the phone ports on OBi#2 one day, or kids may change their mind about having calls ring through to OBi#1.
You could try replacing {(Mcot):aa} with {(Mcot)>**0:aa}
This requires users within cot to send **0 to access aa, the same as dialling from the local phone port. All other calls will ring the phone.
Navigation
[0] Message Index
[#] Next page
[*] Previous page