Obi1022 with Obi202 Ringing Issues
eightminobi:
The word from Vitelity is that you can use sub accounts to route to as many as two devices--beyond that you need a PBX, they said. They said they would help troubleshoot why dual routing is not working on my system.
But this still doesn't help answer the question as to why I can't continue to use single routing from Vitelity and let the OBi202 ring my OBi1022 whenever the OBi202 receives a call...
I'll do another reset on my two OBi units, I'll remove then re-add them to OBiTalk, then I'll reconfigure them. If using the inboundcallroute on the OBi202 doesn't help me to ring both the OBi202 phone and the OBi1022 phone at the same time then I'll re-post here. I don't really think a reset should be necessary (I'd rather troubleshoot the current configuration), but I understand it's probably faster to just reset everything...
Thanks,
Steve
drgeoff:
Did you look at the setting of InboundCallRoute for Obitalk?
eightminobi:
Yes, on the OBi202 it was ph,pp(510123456) (where the OBi number was the correct number for my OBi1022 phone and ph was for the OBi202 device).
drgeoff:
Quote from: eightminobi on June 28, 2016, 01:00:43 pm
Yes, on the OBi202 it was ph,pp(510123456) (where the OBi number was the correct number for my OBi1022 phone and ph was for the OBi202 device).
That is not what I asked.
It is the Obitalk InboundCallRoute on the 1022 that determines what happens to calls coming into the 1022 from the Obitalk network to the 1022's Obitalk 9 digit number..
eightminobi:
What you asked is "did you look at the setting of InboundCallRoute for Obitalk". That question really didn't make sense to me--here's why:
1. There is no global InboundCallRoute setting for "Obitalk". Rather, the InboundCallRoute setting appears on the Obitalk portal under expert configuration for each connected device for an account. As I conveyed extensively, I have two OBi devices: The Obi202 ATA box and the OBi1022 desktop phone. So if you're asking what my "InboundCallRoute for Obitalk" is, I would want to know which device you're talking about (it could be either, my thread concerns both the OBi202 and the OBi1022). Now let's talk about the devices...
2. At Vitelity, I currently have one route defined in my Vitelity account, and that route directs calls arriving on my DID to SubAccount01 (I have two DIDs, but let's just stick to one for now because if I solve the inbound-ring issue for one I can solve it for the other). Once that SubAccount01 was set up, I subscribed my OBi202's SP2 account to that Vitelity SubAccount01. At first, I kept the InboundCallRoute for the OBi202 on the device to simply "ph"... When I placed a test call to my DID, it got routed to the OBi202 ATA box and that device's InboundCallRoute (equal to "ph") caused the phone attached to the first RJ11 phone jack to ring. Fine.
After that succeeded, I registered the new OBi1022 device on my OBiTalk account. It appears on OBiTalk along with my OBi202 device.
Because my DID routes to Vitelity SubAccount01 and because my OBi202 SP2 subscribes and authenticates to that Vitelity SubAccount01, wouldn't it be true that all I need to do to get the OBi1022 to ring is to change the InboundCallRoute of the OBi202 from "ph" to "ph,pp(123456789)"--where 123456789 is the OBi ID of my OBi1022 device? If that device is registered on the ObiTalk network, wouldn't this configuration be sufficient to get my OBi1022 desktop phone to ring??? If no, why?
Thank you,
Steve
Navigation
[0] Message Index
[#] Next page
[*] Previous page