Hook up POTS to Obi2182 via Obi212?
drgeoff:
Quote from: myobinameisinuse9987 on April 26, 2021, 01:59:01 pm
I did find this setting on the 2182
Voice Services / OBiTALK Service / DigitMap :
(<ob>xxxxxxxxx|obxxxxxxxxx)
DigitMap :
(<ob>xxxxxxxxx|obxxxxxxxxx)
Is this what is truncating and blocking our attempts to send numbers to dialout over the 212 from the 2182?
Right above that option at
Voice Services / OBiTALK Service / DisplayName :
Myname 2182
Custom friendly name of device I couldn't locate earlier.
A Voice Service DigitMap is only applied if explicitly invoked. In this case it is not.
Yes the Inbound Direct Dialing Authentication as described on page 122 seems to be present only on the 100/110 devices though there is nothing in the Admin Guide saying that.
myobinameisinuse9987:
Quote from: drgeoff on April 26, 2021, 03:39:03 pm
A Voice Service DigitMap is only applied if explicitly invoked. In this case it is not.
Yes the Inbound Direct Dialing Authentication as described on page 122 seems to be present only on the 100/110 devices though there is nothing in the Admin Guide saying that.
Okay, so we don't have to worry about that DigitMap.
No authentication setting in the 212. Got it. Lacking access to reasonable documentation on the 212, we have to use the other docs for 110 and such. Sometimes it catches us with "undocumented changes"
Does it make a difference if the 2182 and 212 are registered with ObiTalk dot com under different accounts?
Any way to capture the raw characters being passed between devices using the devices? I don't have a sniffer setup here.
This really shouldn't be Rocket Science, but it sure feels like we can't get the rocket off the launch pad here. LOL.
I appreciate the help. I still plan to make up that config guide- once we get it to work.
drgeoff:
No the accounts they are registered to do not matter. In fact I think it should work even without either or both OBis being added to accounts.
What are you currently using for the 212's Obitalk service InboundCallRoute? My second post in this thread (first page in reply to someone else before the thread was hijacked) contains
For outgoing POTS you need to configure both 212 and 2182.
212
Voice Services, OBiTalk Service, InboundCallRoute: {123456789>(xx.):li}
where 123456789 is the 9 digit OBi number of the 2182
myobinameisinuse9987:
Quote from: drgeoff on April 26, 2021, 03:57:07 pm
No the accounts they are registered to do not matter. In fact I think it should work even without either or both OBis being added to accounts.
What are you currently using for the 212's Obitalk service InboundCallRoute? My second post in this thread (first page in reply to someone else before the thread was hijacked) contains
For outgoing POTS you need to configure both 212 and 2182.
212
Voice Services, OBiTalk Service, InboundCallRoute: {123456789>(xx.):li}
where 123456789 is the 9 digit OBi number of the 2182
Thanks for that info.
I started with your InboundCallRoute suggestion. We've gone around the world to get this far and now I am still in your Test Config :
{218211111>:li},{ph} where 218211111 is the 2182 (think this nomenclature will be clearer)
I can try your original if you want? I didn't want to go off in too many directions while we are actively troubleshooting.
I just changed to this :
{218211111>(xx.):li},{ph}
Continue with testing by manually dialing **9212111111*aaabbbcccc ?
Result: Dialed handset on 212
More info:
As soon as we add (xx.) into the InboundCallRoute, the 212 doesn't match the incoming call and dumps it to ph
myobinameisinuse9987:
Give me a bit and I'll setup a fresh 212 and a fresh 1062 and not put them into obitalk dot com, just access directly.
We'll figure it out and strip them down to ONLY doing PSTN gateway and forwarding, then move the lessons over to this system.
There is no way this equipment can be this hard to work with. Starting from scratch seems the wise approach.
I'll be back shortly. Any tips or ideas, let me know.
If there is something else you've always wanted to try out with this setup? After we get this part figured out, let me know.
Navigation
[0] Message Index
[#] Next page
[*] Previous page