News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Hook up POTS to Obi2182 via Obi212?

Started by FlintstoneGummy, March 30, 2021, 08:54:12 AM

Previous topic - Next topic

myobinameisinuse9987

#40
After adding Voice Services / ObiTalk Service / InboundCallRoute :

{tttwwwvvv>(xx.):li}

Same result, Call failed 404 Not Found (or something similar)

tttwwwvvv is Obi number of 2182, no spaces.

Call History of 2182:

From PH1   To PP1(8*+1aaabbbcccc)

Still nothing in Call History of 212

I'm guessing this means 2182 isn't actually SENDING the call to 212, so probably my DigitMap or Outbound route?

drgeoff

#41
You are really not getting it!

If you change the 1 to an 8 in the DigitMap you need to do the same in the OutboundCallRoute.  As azrobert explained that 1 is being changed to the 9 digit number of the 212. That's what <x:y> syntax is all about.

Go and slowly read pages 191 to 203 of the OBi Device Admin Guide. (Yes it is is for the ATAs but the OBiPhones follow the same rules.)  Then read it again.  And once more for good measure.  By then you should understand most of it and know which specific bits to refer to when things are not happening as you expect.

azrobert

#42
If you want to use 8 as the prefix then you must change the outbound route:
{<8:123456789>*(@@.):pp}

I also don't understand why the "+" prefix.

Use this OBi212 OBiTalk inbound route to remove the "+":
OBi212 OBiTalk inbound route:
{111111111>(<+:>xx.|xx.):li}

myobinameisinuse9987

#43
Something has changed. This is what I have in 2182:

123456789 is obi number of 212
987654321 is obi number of 2182

2182 IP Phone / PHONE Settings / DigitMap :
(8*xx.S4|[1-9]x?*(Mpli))

2182 IP Phone / PHONE Settings / OutboundCallRoute :
{<8:123456789>*(@@.):pp}

212 Voice Service / ObiTALK Service / DigitMap :
(<ob>xxxxxxxxx|obxxxxxxxxx)

212 Voice Service / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li}

Result is a Voice: There is no call route available to complete your call

Still nothing in the Call History on 212

Now no new items in call history for 2182


I have read the OBIAdmin Guide section over and over. Still no solution.

Do I have the DigitMap and Call routes on the right devices and under the correct setting?

myobinameisinuse9987

If I didn't want to use any speeddial or maps, etc, what would be the RAW dialing on the 2182 to manually send a call over the 212?

Or better yet, how do I get a dialtone from the line of the 212, using the 2182?


drgeoff

**9 OBi212's 9 digit number * number to be dialled on OBi212's POTS line.

azrobert

#46
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

#47
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

#48
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.)

myobinameisinuse9987

Quote from: drgeoff on April 26, 2021, 10:20:07 AM
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.)

Good idea.

After resetting InboundCallRoute to back to default: {ph}

**9123456789 works from 2182
**9123456789*aaabbbcccc does not (figure it shouldn't until specially allowed to prevent unauthorized use), but interestingly- if allowed to try long enough it eventually dumps to the handset.

So we're back to InboundCallRoute on 212?

azrobert

Try This:
212 Voice Service / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li},{ph}

Calling the 212 should now work.

myobinameisinuse9987

#52
Quote from: azrobert on April 26, 2021, 10:41:12 AM
Try This:
212 Voice Service / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li},{ph}

Calling the 212 should now work.

212 Voice Services / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li},{ph}   where 987654321 is Obi 2182

Calling from 2182 to 212 using :
**9123456789*aaabbbcccc    Rings the phone   where 123456789 is Obi 212

The 212 doesn't seem to be matching the incoming side from the 2182 ?

Call history on 2182 :
To PP1(ob123456789), Ringing, then Call ended (I hang it up)

Call history on 212 :
From 'Myname 2182' PP1(987654321), To PH1, Ringing, Call ended


Also, 8*aaabbbcccc  shows 8*+1aaabbbcccc on the screen of the 2182 and results in Call Failed: 404 Not Found

CallerID on 212 handset when ringing while trying **9123456789*aaabbbcccc from 2182 is the 2812 Obi number



drgeoff

Hmm!  What's with the 'Myname 2182' ?

myobinameisinuse9987

#54
Quote from: drgeoff on April 26, 2021, 11:16:34 AM
Hmm!  What's with the 'Myname 2182' ?

Obi Dashboard / Device Display Name

I didn't find it on the device direct web access, though. Not sure where it is stored, or if it is ObiTalk only thing?

I am power cycling the 2182 and 212. All the config and reboots caused at least one problem on the 2182 earlier. Just to be sure ;)

212 Hardwareversion 1.4, Softwareversion 3.2.2 (Build: 5921EX)

2182 Hardwareversion 1.0, Softwareversion 6.2.3 (Build: 4946.1311)



drgeoff

Quote from: myobinameisinuse9987 on April 26, 2021, 10:55:21 AM
Quote from: azrobert on April 26, 2021, 10:41:12 AM
Try This:
212 Voice Service / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li},{ph}

Calling the 212 should now work.

212 Voice Services / ObiTALK Service / InboundCallRoute :
{987654321>(<+:>xx.|xx.):li},{ph}   where 987654321 is Obi 2182

Calling from 2182 to 212 using :
**9123456789*aaabbbcccc    Rings the phone   where 123456789 is Obi 212

The 212 doesn't seem to be matching the incoming side from the 2182 ?

Call history on 2182 :
To PP1(ob123456789), Ringing, then Call ended (I hang it up)

Call history on 212 :
From 'Myname 2182' PP1(987654321), To PH1, Ringing, Call ended


Also, 8*aaabbbcccc  shows 8*+1aaabbbcccc on the screen of the 2182 and results in Call Failed: 404 Not Found

CallerID on 212 handset when ringing while trying **9123456789*aaabbbcccc from 2182 is the 2812 Obi number



Basic test. Set the 212 Obitalk service InboundCallRoute to

{987654321>:ph}

On the 2182 dial **9987654321.  Does the phone on the 212 ring?

myobinameisinuse9987

Quote from: drgeoff on April 26, 2021, 12:07:34 PM

Basic test. Set the 212 Obitalk service InboundCallRoute to

{987654321>:ph}

On the 2182 dial **9987654321.  Does the phone on the 212 ring?

Yes, phone rings on 212 using that basic test route as the only InboundCallRoute on 212

drgeoff

Quote from: myobinameisinuse9987 on April 26, 2021, 12:19:07 PM
Quote from: drgeoff on April 26, 2021, 12:07:34 PM

Basic test. Set the 212 Obitalk service InboundCallRoute to

{987654321>:ph}

On the 2182 dial **9987654321.  Does the phone on the 212 ring?

Yes, phone rings on 212 using that basic test route as the only InboundCallRoute on 212
Change to

{987654321>:li}

and dial as before.  What happens?

myobinameisinuse9987

#58
Quote from: drgeoff on April 26, 2021, 12:24:05 PM

Change to

{987654321>:li}

and dial as before.  What happens?

Either stutter or two beeps and dialtone

2nd try. Yes, I can dial my cell number from that dialtone

3rd try. Added ,{ph} to InboundCallRoute. Still gets me to dialtone, I can dial out to my cell.

4th try. Dialed 212 obi number from my 202, rings 212 attached handset


So it looks like the 212 InboundCallRoute maybe should just match the FIRST NINE digits? Add x. or x? (not sure, which one says unlimited characters or no characters?)


drgeoff

Does dialling

**9123456789*cell number

on the 2182 ring the cellphone or the 212 phone?