(2) Obi 202's in one place: Distinctive ring and other questions
Chuck_in_ABQ:
I have 2 Obi 202's behind one router, the purpose to allow each family member to have a GV account that rings to the house in addition to their cell. I have a total of 6 GV accounts, plus a basic Anveo account for 911 service. I plan the following assignments:
Obi1:
SP1=old home number (GV)
SP2=My old cell number (GV)
SP2=Wife old cell number (GV)
SP3=Anveo 911 service (no number, just ougoing 911 service)
Obi2:
SP1=child 1 GV
SP2=child 2 GV
SP3=child 3 GV
House phone is connected to ph1 port on Obi1
Some users will also have ObiApps on Android or Ipod devices
I plan to use either of ROnR's setups, http://www.obitalk.com/forum/index.php?topic=1103.0 or http://www.obitalk.com/forum/index.php?topic=2454.20. The second is preferred so it does not rely on Obitalk for local communications (when the handset on obi-1 PH1 is used)
Intent is that all incoming calls on either Obi be routed to PH1 on obi1, as well as to obitalk applications for some users, and preferably with distinctive ringing on all users. Outgoing, home phone account will be used as default. However, if user presses **x, where x is 1, 2, 3, 5, 6, 7, the call will go out through the correct Obi and port (5, 6, 7 are sp1, 2, 3 on obi 2).
A few questions:
1. If I use the SIP version, will that work with all GV accounts like I have? I believe this is straightforward using the obitalk method.
2. I can set distinctive ring on Obi1 for SP1-SP4, plus another for Obitalk source. Is there any way to set additional distinctive rings on the phone connected to obi-1 ph1 port, for the incoming calls from each SPx service on obi2?
3.Can I blend the methods, so that obitalk applications still connect via obitalk, but handset operations use SIP-based direct communication?
Thank you for posting these basic setups, they have helped in a big way!
Chuck
CoalMinerRetired:
Disclaimer: I've only started to play around with the SIP schemes (not the ObiTalk method) you are referring to. So I'm still in the experimenting stage and haven't finalized things yet.
The way you are proceeding is the right way to approach it.
A few answers.
1. For Obi1, I think since Anveo is a true SIP client you're ok. For OBi2 you may need to configure SP4 as a base sip client, 127.0.0.1, etc. There are two more relevant threads that may help with some background, the second of these two specifically discusses the need for a SIP client vs. all GV:
http://www.obitalk.com/forum/index.php?topic=4635.0
http://www.obitalk.com/forum/index.php?topic=4633.0
2. Distinctive Rings. A subject that is under discussed on here, IMO. I guess you already know to edit and associate ring patterns (Ring Pattern 1-10) with an SPX service (X_RingProfile, X_DefaultRing). That is the basic premise.
I've experimented quite a bit with ring patterns, and can add some pointers.
- One big point is the settings (look up Ring Profile A & B Features of the OBi Device in the Device Admin manual) do not act as granular as you would expect. So for example, if you set 0.1 seconds on, and 0.1 seconds off then repeat this for 30 seconds as the cadence you might not get a ring as you'd expect. In some cases the mechanical inertia aspect of the ring-sound producing component in a phone/handset affects this -- even though the ring producing component is all electronic -- the sound might not come out as expected, the ring sound will not stop exactly at 0.1 seconds, and will not start again at exactly 0.2 seconds. This effect of course varies by phone handset used.
- One other thing that seemed inconsistent for me was the way the Obi started the time cycle patterns. For example, I had (still have) one pattern setup as a three ring pattern. It was (.2 sec ring, .1 sec off) repeated there times, i.e., three .2 sec rings with three .1 second off, then wait four seconds, 60;(.2+.1,.2+.1,.2+4). However the initial ring(s) before the first 4 second wait only did two rings, and sometimes the second ring would only have two of the three rings. Experimenting with two or three different handsets let me to conclude it was the Obi not the handsets that were the cause of the inconsistency. The best I can deduce here is the Obi timing in these patterns/cadences is not that accurate or consistent down to the 0.1 second increment.
- Last big point is ring patterns may affect the delivery of Caller ID. Caller ID used in North America is defined as being delivered between the "first and second ring bursts." What is not ever stated here is the rings are assumed to be the usual 2.0 sec ring and 4.0 seconds off cadence/pattern. So an Obi does 'analyze' you custom ring pattern and determine when the first and second ring is, it assumes the standard 2 sec on/4 sec off and send the Caller ID accordingly. The point to take away here is you can make all the custom rings you want, so long as they allow for the Caller ID delivery. Experimenting is the best way to figure out this point. If you get deep into this, there's a suggestion in the feature request section related to this.
3. No experience on my part for this question.
*In hindsight, I'm not sure the distinctive rings will work across SIP connections like this (".. all incoming calls on either Obi be routed to PH1 on obi1"), I presume they will, don't see, can't think of any reason why not.
Hope this helps.
I'll be interested to hear how this all works for you, i.e., reply back and let us know!
Chuck_in_ABQ:
Thanks for the detailed reply, bringing up interesting topics on distinctive rings, which I'll have to explore once I get this all working.
However, it is still unclear to me how to get distinctive rings form obi#2 over to the phone port on obi#1. I guess maybe they would carry forward somehow when Obi#2, sp1 gets routed to obi#1, ph1. I'll have to give that a try.
So far I have only been using the pre-constructed distinctive rings in set A, but may have to adventure out into constructing my own.
I too have just started, still porting all my kid's mobiles to GV (plenty of roadblocks there)
Chuck
CoalMinerRetired:
I'll be very interested to hear how the ring pattern from one Obi to the second Obi scheme works out.
If Obi2 does not send the ring pattern to Obi1, then there's this blurb in the Device Admin manual, that maybe -- I can't picture how at the moment -- you insert a message into the call transfer to the Obi1 with the appropriate URI mentioned:
Quote
ITSP Driven Distinctive Ringing
OBi device offers 10 ring and 10 call-waiting tone patterns in each ring profile. These patterns are numbered from 1 to 10. Each pattern also comes with a configurable name. A different default ring may be assigned to each trunk on the device.
An ITSP can tell OBi device which ring to use by name for a call routed to SP1/SP2 by inserting an Alert-Info header in the SIP INVITE sent to the device. The Alert-Info must include a URI. For example:
Alert-Info: http://www.xyz.com/some-folder/bellcore-dr4
When the device receives this, it will look for a ring tone name or call-waiting tone name in the ring profile that matches the Alert-Info URI. Ring tone names are compared case- insensitively. If a match is found, device plays the corresponding ring or call-waiting tone. Otherwise, device plays the default ring.
The other thing I think (and hope) you can do is get a direct dial of "911" on Obi2 to automatically forward to and dial out on SP4 on Obi1. From some experimenting I've done, I think you can do this using one User Defined Digit Map in Obi2. Please do report back on this point, and if or when you get to it post up any questions.
What you're attempting is, from my POV, the more interesting thing I've seen attempted on here since I've gotten into it.
Chuck_in_ABQ:
I get my second Obi tomorrow, probalby cannot play with setup until Friday. I'll report my findings. Sounds like I can force a ring pattern, but it is not clear how. Would be happy to force one of the 10 on the Obi, not have to go to a URL. Maybe someone from OBI can clarify how.
Plan is as you say on 911. One option might be to have both obi's have the Anveo account on port 4, but I am not certain that is a good idea. Further, outgoing calls are going to be form landline (ph1 on obi1), and that is the critical one to have go to 911. It is incoming routing, plus **x (1 to 6) for outgoing callerID, all from one handset, that I want. 911, there really is no need to route form Obi2 to Obi 1. Possibly if an obi app is talking, but it can go to obi1 directly anyway.
Chuck
Navigation
[0] Message Index
[#] Next page