Hook up POTS to Obi2182 via Obi212?
drgeoff:
**9 OBi212's 9 digit number * number to be dialled on OBi212's POTS line.
azrobert:
Change the 2182 IP Phone / PHONE Settings / DigitMap :
(8*xx.S4| <rest of the phone digit map>
Rest of the digit map does Not have a beginning parenthesis.
What is your Primary line and please post it’s digit map
The message you’re getting indicates no match on the outbound route.
I don’t see the cause.
Edit:
I want you to remove [1-9]x?*(Mpli)| from the digit map
myobinameisinuse9987:
Quote from: azrobert on April 26, 2021, 09:36:04 am
Change the 2182 IP Phone / PHONE Settings / DigitMap :
(8*xx.S4| <rest of the phone digit map>
Rest of the digit map does Not have a beginning parenthesis.
What is your Primary line and please post it’s digit map
The message you’re getting indicates no match on the outbound route.
I don’t see the cause.
Edit:
I want you to remove [1-9]x?*(Mpli)| from the digit map
Ok, so I've been troubleshooting that digit map. Found out my left side buttons, setup as Monitor for the other 2182 using extension as just 40 didn't work. Also found the latest ObiTalk configuration wasn't downloading to the phone, so I power cycled the 2182 and reset DigitMap and OutboundCallRoute to default. Extensions worked again.
Modifying ONLY the DigitMap, I made changes to implement the suggestions, now able to use the extension button to test syntax.
This is what I know have for DigitMap:
(8*xx.S4|[1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|***|**0|#|##|**70(Mli)|**8(Mbt)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**6(Msp6)|**9(Mpp)|(Mpli))
My extension buttons work. Adding that 10-digit dialing to outside number also works. I am taking this as "Your DigitMap syntax is okay"
Does it match okay with what you suggest for using 8* to route to the 212? If so, I'll start on the OutboundCallRoute.
Thanks.
myobinameisinuse9987:
Quote from: drgeoff on April 26, 2021, 09:03:01 am
**9 OBi212's 9 digit number * number to be dialled on OBi212's POTS line.
I tried this, attempting to confirm the InboundCallRoute on 212 was correct:
**9123456789*aaabbbcccc where 123456789 is Obi number of 212 and aaabbbcccc is my cell number
Response:
Call Failed: Busy
To: **9ob123456789
Maybe if we can get this working, the other parts will fall into place?
Additional info:
**9123456789 also failed
**9456789123 works, where 456789123 is number of my other 2182
So it now looks like it is back to the 212 InboundCallRoute, which is currently :
{680370145>(<+:>xx.|xx.):li}
I probably have the syntax wrong there, too?
Please remember, I still want to be able to call the ph ext on the 212 to use as intercom. Not sure what has to happen to not simply dump everything from 2182 to the line port on 212? It's okay to test it with a full dump for now.
drgeoff:
Quote from: myobinameisinuse9987 on April 26, 2021, 10:07:49 am
**9123456789 also failed
**9456789123 works, where 456789123 is number of my other 2182
On the 212, set the OBitalk Service InboundCallRoute back to the default ph. If **9123456789 fails you have some problem with the 212 or its network connection. You are plugging the ethernet cable into its INTERNET jack? (The LAN one will not work unless you change the 212 from router mode to bridge mode.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page