Obi1022 with Obi202 Ringing Issues
SteveInWA:
Quote from: eightminobi on June 25, 2016, 11:30:16 pm
Hi,
Vitelity does support sub accounts. I created a new one and changed the registration of the OBi1022 to it. Then I used Vitelity's route feature to route calls from my DID to the original sub account as well as to the new sub account.
Still, only the original sub account rang (i.e., the phone attached to the OBi202). When I removed the original account as a route, the OBi1022 rang...
It seems that Vitelity doesn't route to two sub-accounts simultaneously--it seems that it "hunts" between the two (and two is the maximum number of sub-accounts you can define--at least at my Vitelity subscription level).
The new sub-account is working for out-bound calls on the OBi1022, so I kept the sub-account. Now I can make outbound calls from either my Panasonic (attached to the OBi202) or from the OBi1022 phone.
To try to get both phones to ring simultaneously, I again went to the inbound route setting for SP2 on the OBi202 expert configuration page. I used your example:
ph,pp(510123456)
and changed the 9 digit number to the OBi number for my new OBi1022 phone. Still, only the Panasonic rang. When I remove ph, then I get to an auto attendant...
I don't really understand how pp(<obi number>) works. I get that it copies an inbound call and directs it to that OBi device, but since my device is a 1022 phone, I want the call to come in on Line 2, which corresponds to SP2 (the SP# I am configuring to ring on both devices).
Do you know why I'm getting connected to the AA?
How can I make Line 2 ring when using the pp(123456789) syntax???
Thank you,
Steve
This sounds fishy.
Given that they support sub accounts, the main purpose of doing so is to allow multiple, distinct SIP registrations, with, in your case, two different SIP user agents (the 202 and the 1022). It is expected that outbound calls would work from both devices; the key issue is that having distinct SIP registrations will allow you to have two different inbound call paths. It's possible that you need to change the SIP port used by the second user agent. It's also possible that the customizations you made have broken this functionality.
Why don't you contact them for assistance? I can tell you that this works perfectly with my ITSP, Callcentric. It should work equally well with Vitelity.
drgeoff:
Quote from: eightminobi on June 25, 2016, 11:30:16 pm
I don't really understand how pp(<obi number>) works. I get that it copies an inbound call and directs it to that OBi device, but since my device is a 1022 phone, I want the call to come in on Line 2, which corresponds to SP2 (the SP# I am configuring to ring on both devices).
Do you know why I'm getting connected to the AA?
How can I make Line 2 ring when using the pp(123456789) syntax???
1. The Obitalk network is a 'Line' in its own right, on a par with the other SPs. So a call forwarded to ob123456789 will not come in to OBi device 123456789 on SPx (SP1 to 6 on 1 1022.)
2. The OBitalk 'Line' has its own InboundCallRoute. Check (on the 1022) that is set to ph. It may have been changed to aa.
eightminobi:
@drgeoff: Thanks, but I don't understand the bolded text...
So a call forwarded to ob123456789 will not come in to OBi device 123456789 on SPx (SP1 to 6 on 1 1022.)
I just would like to know how I direct an incoming call to the OBi1022 device's Line 2. If I only can direct to device ph on the 1022 or to the aa on the 1022, then fine--I suppose the call just comes in on the first available slot (by "slot", I mean the 5 phone-line entries on the right side of the display)... Ideally, I wanted calls from SP1 to route to Slot 1, calls from SP2 to route to Slot 2, etc. But then I'm not sure what I would want to happen if I am already using Slot 1 for another inbound or outbound call. Again, I am thinking of AT&T land-line behavior, in which case the caller would receive a busy signal (i.e., I'm on the line), I would get a call-waiting tone, or they would route to a "line-in-use" voice-mail message--or the incoming could hunt to the next available slot... Gee, this stuff gets complicated quickly...!
SteveInWA:
Unfortunately, there is no "bang head on table" emoticon in this forum editor.
I am willing to bet that this is a case of an engineer trying to "engineer" a solution that doesn't need to be "engineered". There is no need to do any digit map or call route changes, and, in fact, you have probably changed something that is now conflicting with using two different SIP registrations (sub accounts).
Just do this; it will take far less time than you have already spent.
1: Contact Vitelity and confirm with them that they support concurrent use of multiple sub accounts, and that both sub accounts will independently ring on inbound calls (that's the whole point of having them). If this isn't the case, then Vitelity sucks, and you can take your business to a better ITSP, like voip.ms or Callcentric.
2: Log into the OBiTALK web portal. Delete both of your devices off of the portal. Gone. Bye-bye.
3: Factory reset both devices, by dialing ***8, then 1 to confirm. Wait plenty of time for each device to fully reset and reboot.
4: You must get two separate extensions (aka sub-accounts) for each of your two DID numbers. Add both devices back to the portal, using the **5 procedure. Use the portal, not the local web interface, to configure your two Vitelity DID sub accounts per device (On the OBi 202, DID #1 extension 1, on SP1, and DID #2, extension 1, on SP2; on the OBi 1022, DID #1, extension 2 on SP1, and DID #2, extension 2, on SP2). To do this, click each SP, accept the warning about 911, scroll down to the bottom of the page, click "OBiTALK Compatible Service Providers", and then, on the next page, click "Vitelity".
5: You're done. It should simply work. If it doesn't work, change ITSPs.
eightminobi:
There has been no over-engineering: Sometimes things that *should* work, don't. That doesn't mean that the person is over-engineering a solution or making things more complicated. I will contact Vitelity tomorrow. It is of course entirely possible that their "sub accounts" don't work the way they do for other ITSP (although that would be rather strange)--but it also might be a limitation based on my subscription level, etc. If they can't do it then I can switch ITSPs.
But until I ask questions here, I can't know whether I'm doing something wrong or not. For the record, I did in fact save the configurations for the OBi202 and 1022 before resetting them and trying again--still no luck. So all fingers seem to be pointing to Vitelity at this point.
Thank you,
Steve
Navigation
[0] Message Index
[#] Next page
[*] Previous page