OBiTALK Community

Hi all - first off, thanks to this forum for helping me figure out the maddening mess of how to configure these darned devices. Trying to help out my in-laws with a weird config question.

Let me describe the situation:

• I have an Obi2182 - works totally fine
• I have an Obi212 - also works totally fine
• In-laws have a landline phone, call it 123-456-7890 that they will not, under any circumstances, port to a VOIP provider
• That being said, they like the idea of being able to access that landline on the Obi2182

So my question is... can I hook up the landline POTS to the Obi212, and bounce all incoming and outcoming calls via the Obi network to the Obi2182? Ie. I can receive calls coming into 123-456-7890 via the Obi2182, and place calls coming from 123-456-7890 via the Obi2182 by using the Obi212 to access the POTS line?

Quote from: FlintstoneGummy on March 30, 2021, 08:54:12 AM
Hi all - first off, thanks to this forum for helping me figure out the maddening mess of how to configure these darned devices. Trying to help out my in-laws with a weird config question.

Let me describe the situation:

• I have an Obi2182 - works totally fine
• I have an Obi212 - also works totally fine
• In-laws have a landline phone, call it 123-456-7890 that they will not, under any circumstances, port to a VOIP provider
• That being said, they like the idea of being able to access that landline on the Obi2182

So my question is... can I hook up the landline POTS to the Obi212, and bounce all incoming and outcoming calls via the Obi network to the Obi2182? Ie. I can receive calls coming into 123-456-7890 via the Obi2182, and place calls coming from 123-456-7890 via the Obi2182 by using the Obi212 to access the POTS line?

You have not explicitly confirmed that the you and your in-laws are in the same premises but if not it isn't easy to understand what you want.

Yes you can route 2182 POTS calls in and out via the 212 over the Obitalk network.

Quote from: drgeoff on March 30, 2021, 09:56:30 AM
You have not explicitly confirmed that the you and your in-laws are in the same premises but if not it isn't easy to understand what you want.

Yes you can route 2182 POTS calls in and out via the 212 over the Obitalk network.

When I say "I have" i meant "they have" ;D

So yes, you can consider it the same premises.

How do you route 2182 POTS calls in and out via the 212 over the Obitalk network? That's basically what I am trying to do.

Quote from: FlintstoneGummy on March 30, 2021, 10:04:55 AM

Quote from: drgeoff on March 30, 2021, 09:56:30 AM
You have not explicitly confirmed that the you and your in-laws are in the same premises but if not it isn't easy to understand what you want.

Yes you can route 2182 POTS calls in and out via the 212 over the Obitalk network.

When I say "I have" i meant "they have" ;D

So yes, you can consider it the same premises.

How do you route 2182 POTS calls in and out via the 212 over the Obitalk network? That's basically what I am trying to do.

For incoming POTS you only need to change one setting on the 212.

Physical Interfaces, Line Port, InboundCallRoute: ph,ob(123456789) ph,pp(123456789)

Replace 123456789 with the 9 digit OBi number of the 2182.

Incoming POTS calls will ring both the phone on the 212 and the 2182. Either can answer.  If you don't want the 212's phone to ring just use ob(123456789) pp(123456789).

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

2182
Physical Interfaces, Phone Port, DigitMap
It begins: ([1-9]x?*(Mpli)
Insert 1*xx.S3| to make it begin (1*xx.S3|[1-9]x?*(Mpli)

Physical Interfaces, Phone Port, OutboundCallRoute:
It begins: {([1-9]x?*(Mpli)):pp}
Make insertion so that it begins: {(<1:987654321>*(xx.)):pp},{([1-9]x?*(Mpli)):pp}
Replace 987654321 with the 9 digit OBi mumber of the 212.

Dial 1*8005551212 on the 2182 and 8005551212 will be called on the POTS line.

(With acknowledgement to azrobert from whom some of this was cribbed.)

Edited to correct errors pointed out and acknowledged in posts below.

THANK YOU!

I tried it and it works!!!!!!

QQ: now I'm just being fancy here, but is there a way to get the landline (123-456-7890) to show up on the right line line keys, so I can skip the "1*" and dial out directly?

EDIT: I figured it out! The instructions are here (http://www.obitalk.com/forum/index.php?topic=7030.0) under the heading "Mini PBX – Two OBi ATAs With One PSTN Line"

Thank you thank you thank you!!

Quote from: FlintstoneGummy on March 30, 2021, 11:30:01 AM
THANK YOU!

I tried it and it works!!!!!!

QQ: now I'm just being fancy here, but is there a way to get the landline (123-456-7890) to show up on the right line line keys, so I can skip the "1*" and dial out directly?

Yes that should be possible but is not something I have already tried and tested.  It may be several days before I'm able to do that.  If you want to try:

1. You need to explicitly select the Obitalk network.  See page 75 of the Admin Guide https://www.obitalk.com/info/documents/admin_guide/OBiPhoneAdminGuide.pdf.  Probably you'll elect to bind a Call Appearance key to the Obitalk service.

2.  Configure the Obitalk Service DigitMap to prepend 987654321* to dialled numbers containing other than 9 digits.  (That means that dialling 9 digit OBi numbers will continue to work as before.) See page 217 onwards and the second row of the table on page 222 has an example of prepending.

Of course you would still need to press the relevant LINE key before dialling so that would not take less keypresses than keying, say, a * or # before a number.  In which case an alternative to the two above paragraphs is to merely change one part of what I wrote in my previous post.

2182
Physical Interfaces, Phone Port, DigitMap
It begins: ([1-9]x?*(Mpli)
Insert <*:1*>xx.S3| to make it begin (<*:1*>xx.S3|[1-9]x?*(Mpli)

Now keying an initial * will cause the following digits to be dialled on the POTS line.

Change the <*:1*> to <#:1*> if you prefer to use an initial #.

Bigelow567 is a SPAMMER.  His post above is a verbatim copy of mine at http://www.obitalk.com/forum/index.php?topic=13651.msg87650#msg87650.  What I wrote there is irrelevant to this thread.

Quote from: drgeoff on March 30, 2021, 10:47:14 AM
For incoming POTS you only need to change one setting on the 212.

Physical Interfaces, Line Port, InboundCallRoute: ph,ob(123456789)

Replace 123456789 with the 9 digit OBi number of the 2182.

Incoming POTS calls will ring both the phone on the 212 and the 2182. Either can answer.  If you don't want the 212's phone to ring just use ob(123456789).

Let me ADD to the post quoted. On the OBi212, the only way I could get it to work was to use the below for InboundCallRoute, where 123456789 is replaced with my OBi1062 number.

ph,PP(ob123456789)

Using ph,ob(123456789) or even just ob(123456789) didn't work for me. No way, no how.

Can I also add additional OBi's to the list without problems? Is there some reason I couldn't get it to work as posted by Drgeoff, or was it just incomplete or a typo?

Thanks.

Yes, an error on my part. The correct forms for routeing to an OBi number are

pp(123456789)

pp(ob123456789)

The pp and optional ob may also be in upper case.

Quote from: myobinameisinuse9987 on April 20, 2021, 06:07:41 PM
Can I also add additional OBi's to the list without problems? Is there some reason I couldn't get it to work as posted by Drgeoff, or was it just incomplete or a typo?

Yes you can add additional OBis to the list.  Somewhere the documentation mentions a limit of four destinations in an InboundCallRoute.

Thanks drgeoff.

Now that we're doing more things with the OBi's, have to do more complex configurations. Syntax documentation seems hard to find. Is there a "Master List" document for syntax, keywords, etc?

Four destinations? That works great for me.

For someone who has already forwarded a connection to another device, they would automatically know to add the 'pp' but for my first attempt, I didn't know. Thanks for confirming the solution.

Quote from: myobinameisinuse9987 on April 21, 2021, 12:45:43 PM
Thanks drgeoff.

Now that we're doing more things with the OBi's, have to do more complex configurations. Syntax documentation seems hard to find. Is there a "Master List" document for syntax, keywords, etc?

Four destinations? That works great for me.

For someone who has already forwarded a connection to another device, they would automatically know to add the 'pp' but for my first attempt, I didn't know. Thanks for confirming the solution.

The Admin Guide available from the Docs section of obitalk.com has lots of info. There is also a good tutorial on Digit Maps and call routeing.

Quote from: drgeoff on April 21, 2021, 02:45:08 PM

The Admin Guide available from the Docs section of obitalk.com has lots of info. There is also a good tutorial on Digit Maps and call routeing.
[/quote]

Thank you.

Can you tell me (I've searched and searched and....)

Does OBi212 support 2-line phones into the line port OR out to a 2-line phone via the phone port?
Does OBi202 support out to a 2-line phone via the phone port(s), using a single 2-line wire (2-pair)?
Does OBi212 pass CallerID to other OBi devices, when using InboundCallRoute?

FYI. I called Poly last week to ask about features of 312 vs 212. They were spectacularly UN-knowledgeable. So we're it, guys. Help each other out.

Thanks.

The OBi212 has no support for two line phones.  The PHONE jack is wired for one phone.  The LINE jack is wired for one POTS type line.  Electrically the OBi212 has 1 FXS and 1 FXO port.

The OBi202 supports a two line phone.  Connect a two line phone using a 4 conductor cord into the PHONE1 jack of the OBi202 or by using two 2 conductor cords - one into PHONE1 jack and one into PHONE2 jack. Electrically the OBi202 has 2 FXS ports.

Yes, the OBi212 passes CallerID to other OBis when using InboundCallRoute.

The OBi312 is identical to an OBi212 except that the 312 does not support Google Voice.  (Ditto for the 302/202 and 300/200 pairs).

Thank you for the definitive answers ;)

I have another challenge, if you wish.

I'm using the InboundCallRoute now. In my plan, I have to change for 5 locations to ring on incoming 212, including the local ph port on the 212.

You said it was limited to 4.

It made me wonder if I can take one of the 1062 phones that rings from the 212 InboundCallRoute and somehow make it ring that 5th device? Daisy chain, if you will.

Yes, I know that if that device is offline, the chain will break. But I'm dealing with a hybrid of analog and VoIP, customer choice and 2yr landline contract.

I can easily do 5 ring locations from Anveo with any VoIP lines, but these analogs...

Thanks!

Quote from: myobinameisinuse9987 on April 23, 2021, 10:48:32 AM
Thank you for the definitive answers ;)

I have another challenge, if you wish.

I'm using the InboundCallRoute now. In my plan, I have to change for 5 locations to ring on incoming 212, including the local ph port on the 212.

You said it was limited to 4.

It made me wonder if I can take one of the 1062 phones that rings from the 212 InboundCallRoute and somehow make it ring that 5th device? Daisy chain, if you will.

Yes, I know that if that device is offline, the chain will break. But I'm dealing with a hybrid of analog and VoIP, customer choice and 2yr landline contract.

I can easily do 5 ring locations from Anveo with any VoIP lines, but these analogs...

Thanks!

The limit of four is in the first of the Notes at the bottom of page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf.  I have never verified this so you might want to try five - perhaps the newer 2xx series OBis are not as processor bound as the 1x0 devices were.  If five does not work I see no reason why the daisy chain method would not.

Note that you probably need to up the "MaxSessions" from the default 2 in the 212's Obitalk Service, Calling Features.

Quote from: drgeoff on April 23, 2021, 12:36:57 PM
The limit of four is in the first of the Notes at the bottom of page 193 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf.  I have never verified this so you might want to try five - perhaps the newer 2xx series OBis are not as processor bound as the 1x0 devices were.  If five does not work I see no reason why the daisy chain method would not.

Note that you probably need to up the "MaxSessions" from the default 2 in the 212's Obitalk Service, Calling Features.

I'll take a look at that section in the AdminGuide, thanks for the link. I didn't realize the Notes sections were for "reading" LOL. This is the guide where I found the 'PP' syntax in previous posts.

What would you recommend for MaxSessions? I haven't come across any criteria yet, or how to figure it out. Will this be affected by OUTBOUND calls from the 1062's that I plan to allow to dial out on the 212 ?

As I understand it, setup Trunk on 212 Li interface, then pass from 1062 to the 212. From what I understand, this is to require password to prevent unauthorized usage of Line interface on 212 (presumably from an errant Transfer from a user?)

I saw the suggestions early in this thread but haven't tried and tested it yet. I plan to test tonight/tomorrow with a 212 and 2182 I have here.

Fyi- YES, you can use FXS port of OBi202 as FXO line in on OBi212, although any calls passing there come up RESTRICTED. Perhaps due to GV being on that line?

Again, thank you for all the help.

(BTW, nice syntax help in that section of the guide, too)

If you will be forking to four other OBis using the OBiTALK service then I would set MaxSessions to 4.  This is only relevant to calls coming into the 212's LINE port (and ringing its PHONE port and being forked to four other OBis.  Regarding outgoing calls on the 212's LINE port there can only be one at a time!

Some protection would be a good idea to prevent any other OBi on the planet coming in over the OBiTALK network to the 212 and calling out on the POTS line.  See page 19 of the tutorial I mentioned above.

Yes the LINE and PHONE ports conform quite well to FXO and FXS standards so no surprise that you can connect them together though I cannot immediately think why RESTRICTED  would come up.

There is a hack you can use for more than 4 destinations. You need an open SP to do this easily. Your inbound route will send the call to 3 destinations. The 4th will be looped out say SP4 and back into SP4. The SP4 inbound route will send the call to the 4th and 5th destinations.

Setup dummy trunk:
Service Providers -> ITSP Profile D -> SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile D -> SIP -> X_SpoofCallerID: Checked
Voice Services -> SP4 Service -> AuthUserName: anything
Voice Services -> SP4 Service -> X_RegisterEnable: unchecked
Voice Services -> SP4 Service -> X_ServProvProfile: D

Inbound route:
dest1,dest2,dest3,sp4(0@127.0.0.1:5063)
5063 is the X_UserAgentPort
5063 is the default, but might get changed to 5083 with GV setup

SP4 inbound route
dest4,dest5

Quote from: azrobert on April 23, 2021, 03:58:06 PM
There is a hack you can use for more than 4 destinations. You need an open SP to do this easily. Your inbound route will send the call to 3 destinations. The 4th will be looped out say SP4 and back into SP4. The SP4 inbound route will send the call to the 4th and 5th destinations.

Setup dummy trunk:
Service Providers -> ITSP Profile D -> SIP -> ProxyServer: 127.0.0.1
Service Providers -> ITSP Profile D -> SIP -> X_SpoofCallerID: Checked
Voice Services -> SP4 Service -> AuthUserName: anything
Voice Services -> SP4 Service -> X_RegisterEnable: unchecked
Voice Services -> SP4 Service -> X_ServProvProfile: D

Inbound route:
dest1,dest2,dest3,sp4(0@127.0.0.1:5063)
5063 is the X_UserAgentPort
5063 is the default, but might get changed to 5083 with GV setup

SP4 inbound route
dest4,dest5

That is very logical to forward it directly within the 212 itself. I'm guessing the SP4 also allows 4 InboundCallRoute locations, making it 7 locations?

Any delays expected? Do I need to increase MaxSessions or anything else for the extra SP4 processing?

Thank you!

With the help you guys are giving, this system is really coming along.

Yes, 7 destinations. I never tried it, but I assume you can loop a 2nd time making it 10 destinations.

I don't expect any delays, but I've been wrong before. I only tried looping in a test environment and didn't detect any delays.

I didn't read this entire thread, so I don't know where you're routing calls. If all the calls are routed to the OBiTalk network then the Maxsessions on OBiTalk must be increased. Maxsessions must be equal or greater than the max number of simultaneous calls on a service. You are routing the call out SP4 then back in SP4, so that is 2 simultaneous calls on SP4. The SP4 default of 2 is OK.

Okay, some delays on the testing while setting up the test equipment....

When using InboundCallRoute to ring other devices, is there a way to prepend to the CallerID data?

I'd like to add the last 4 digits of the incoming line (which I know because it is fixed on a 212) and then the incoming callerID.

That way even the cordless analog phones will know which line is calling.

Why? Few people, cover to answer for each other ad-hoc. Walk away from desk, go into warehouse, talking to customer, etc.

Since I'm sending calls from 212 over ObiTalk network, should be able to do it?

Thanks.

Quote from: myobinameisinuse9987 on April 24, 2021, 09:50:31 AM
Okay, some delays on the testing while setting up the test equipment....

When using InboundCallRoute to ring other devices, is there a way to prepend to the CallerID data?

I'd like to add the last 4 digits of the incoming line (which I know because it is fixed on a 212) and then the incoming callerID.

That way even the cordless analog phones will know which line is calling.

Why? Few people, cover to answer for each other ad-hoc. Walk away from desk, go into warehouse, talking to customer, etc.

Since I'm sending calls from 212 over ObiTalk network, should be able to do it?

Thanks.

http://www.obitalk.com/forum/index.php?topic=11192.0

Time you learned how to use a search engine.  You are getting towards the end of my free advice to those who make a profit from it.  :)

Quote from: drgeoff on April 24, 2021, 10:37:16 AM

http://www.obitalk.com/forum/index.php?topic=11192.0

Time you learned how to use a search engine.  You are getting towards the end of my free advice to those who make a profit from it.  :)

I hear you and appreciate your position. I am perfectly happy to search and read any links.

Point me towards a helpful search engine and I'll use it. LOL. Anything on open internet that has Obi in it yields Obihai and Polycom items, doesn't care what other terms I add. I tried "prepend callerID" "forward callerID" and about 6 other combinations of terms.

So your links and explanations are EXTREMELY helpful and I only ask after investing a significant amount of time trying to find the info first.

But here's something: I find a LOT of lacking info on the 212. I believe you have mentioned in other thread(s) that you don't have one on hand. Others have the same problem getting one.

They have some quirks, which I am compiling and intending to open a How-to thread on the 212, to include what we're doing with them and the tips and tricks we're finding. (By we, it is my daughter (intern) and I, 2-people)

I know that doesn't directly pay you back, but hope it does further the spirit of paying it forward.

An example: The 212 does not support 10-digit dialing out of the box (factory reset, no FW updates available). This area code is old. Some exchanges are local, some are long distance, no 7-digit dialing, no rhyme or reason for Verizon.

So I modified the Dialing Map as follows: Physical Interfaces/ Line/ Line port/ Digit map: (xxxxxxxS4|1xxxxxxxxxx|xxxxxxxxxx|xx.)

I added the 10-digit rule. Simple, I know, but a real pain.

Should have been 1) plug line from wall into Line on 212, 2) Plug phone into Phone on 212, even with no power allow the relay to connect those ports and do a test call.

Nope. :(

Obi212 didn't connect the two ports. 10-digit dialing didn't work (I didn't know this until after they tried to use it and couldn't dial out). 1-(10digit) worked fine, which is what I tested.

I consider that a gotcha. Some speculate about the relay for the two ports on Obi212. I will be testing another one shortly.

The InboundCallRoute tips are helpful.

All said, I REALLY appreciate the help! If I can return the favor, let me know and how.

I can't get that Map for X_InboundCallingRoute to work for CID modifications any which way on OBi202.

I tried for hours and many combinations.

I removed the ph for testing so the cordless Panasonic would only ring with the single rule.

This is on my personal system, to separate business calls from personal calls. Want to add 1-3 numbers at beginning of CID.

The different ring tones are hit and miss with the cordless handsets.

Any ideas or updates to the 2016 version above?

Thanks.

Quote from: myobinameisinuse9987 on April 25, 2021, 10:21:18 AM

This is on my personal system, to separate business calls from personal calls. Want to add 1-3 numbers at beginning of CID.

Give the following a try:

{(<:555>xx.):ph}

Quote from: Taoman on April 25, 2021, 11:34:12 AM

Give the following a try:

{(<:555>xx.):ph}

No joy. Phone didn't ring. But I did confirm with

{(<:555>xx.):ph},ph

that phone, port, etc are all correct. Doesn't seem to be matching correctly?

Did Obi remove this capability? Incoming is GV line (shouldn't matter?), going out over phone port2 on the Obi202. I haven't updated firmware in quite some time?

It does matter, GV prepends a "+".
Try:
{(<+:555>xx.):ph}

Quote from: azrobert on April 25, 2021, 02:30:00 PM
It does matter, GV prepends a "+".
Try:
{(<+:555>xx.):ph}

Okay, that is a step closer. It rings in on that line now, but not CID changes.

On the Panasonic cordless CID is 1-aaa-bbb-cccc, where a=Area code, b=Exchange, c=last 4
On the Obi2182, CID is +1aaabbbcccc (I see the + and no dashes)

I have been checking the 2182, just in case the Panasonic cordless is funky with CID.

Ok, HOLD THE PHONE...

{(<+:=555>xx.):ph}

Yields 5551aaabbbcccc  on the second screen, nothing on the first screen (too wide).

But, found another problem with the test setup.

This Panasonic phone and the Obi202 used have been in service for quite some time. (the 2182 is new to us just this week). Because of that, something I never checked, is my cell that is being used to call and test the CID changes was saved in the phone's directory/phonebook.

We've had this cordless phone for a decade I think. It had 4 items in its onboard phonebook. I forgot it even had one.

So, that means the above works (I added the = ), but it also means the other suggests are NOT EXCLUDED, they may work, I can't say with any certainty due to a defective test setup.

To anyone else looking to modify incoming callerID, be sure there isn't any store numbers, phonebook, directory, etc on your phone used for testing. At least on this Panasonic cordless, it will override any incoming CID.

Thank you to all who have helped me get this far!

You don't need to see the + or the country code.
This worked on my OBi1032 IP Phone:
{(<+1:*>xxx<->xxx<->xxxx):ph},{ph}

Quote from: myobinameisinuse9987 on April 25, 2021, 03:58:31 PM
Ok, HOLD THE PHONE...

{(<+:=555>xx.):ph}

Yields 5551aaabbbcccc  on the second screen, nothing on the first screen (too wide).

Try the following:
{(<+1:12>xxxxxxxxxx):ph} should be visible on the Panasonic
{(<+1:1234>xxxxxxxxxx):ph} should be visible on the OBi2182

If your incoming calls are mostly from one or two area codes there is additional digit manipulation you can do so the 4-digit prepend number will show up on the Panasonic (minus the area code).

{(<+1555:1234>xx.):ph},{(<+1666:1234>xx.):ph},{ph}

Okay, here is the "Big List of CID Attempts and Results using Google Voice (GV) on Panasonic cordless phone connected to OBi202"

My actual number last 4-digits start with 0, seems to funk things up in places, so I tried a 1. Anonymized my number to be: aaa-bbb-cccc or last 4 as 5678

{(<+:=555>xx.):ph}  / Works!!!

{(<x:3>xxxxxxxxxx):ph}   /Doesn't match to ring

Google Voice requires + in front (adds to CID) to match

{(<+x:3>xxxxxxxxxx):ph}   /WORKS!!! 3-aaa-bbb-cccc on first, main screen

{(<+x:3>xxxxxxxxxx):ph},{ph}   / WORKS! 3-aaa-bbb-cccc displayed. extra {ph} catches odd calls if miss the match

{(<+x:h>xxxxxxxxxx):ph},{ph}   / Matches and rings. PRIVATE CALLER displayed

{(<+x:5678>xxxxxxxxxx):ph},{ph}   / Matches and rings. PRIVATE CALLER displayed

{(<+x:78>xxxxxxxxxx):ph},{ph}   / Matches and rings. 78aaabbbcccc displayed, no dashes

Noticed some stuff on 2nd page of CallerID upon checking call log

{(<+x:1678>xxxxxxxxxx):ph},{ph}   / Matches and rings. 1678aaabbbcc.. displayed on first page, no dashes. On second page, last 2 cc on second line.

{(<+x:678>xxxxxxxxxx):ph},{ph}   / Matches and rings. 678aaabbbccc. displayed on first page, no dashes. On second page, last 1 c on second line

{(<+x:2>xxxxxxxxxx):ph},{ph}   / Final Solution for SP2 (home) 2-aaa-bbb-cccc displayed on first page, with dashes (final, for now ;) )

{(<+1:*>xxx<->xxx<->xxxx):ph},{ph}   / *-aaa-bbb-cccc

{(<+1:12>xxxxxxxxxx):ph}   / 12aaabbbcccc  No dashes

I know examples help me understand syntax, maybe this list will help someone.

So as I try to finish the 212 setup, I want to be able to dial a prefix on any analog phones attached to OBi phone port, or press a Line button on Obi1062 and be able to dial out using the LINE port on one of the 212's.

I wish to retain ability to call the OBi212 ph analog phone as an extension.

I've tried using my 2182 and 212 here using drgeoff's instructions here:

Quote
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

2182
Physical Interfaces, Phone Port, DigitMap
It begins: ([1-9]x?*(Mpli)
Insert 1*xx.S3| to make it begin (1*xx.S3|[1-9]x?*(Mpli)

Physical Interfaces, Phone Port, OutboundCallRoute:
It begins: {([1-9]x?*(Mpli)):pp}
Make insertion so that it begins: {(<1:987654321>*(xx.)):pp},{([1-9]x?*(Mpli)):pp}
Replace 987654321 with the 9 digit OBi mumber of the 212.

Dial 1*8005551212 on the 2182 and 8005551212 will be called on the POTS line.

I can't get it to work. On the Obi2162 I dial

1*aaabbbcccc  which gives a Trying message, then Call Failed 900.

The Line port on the 212 does not blink. I have tested it by dialing out on it from 212 phone port using analog phone. It is GV and allows 10-digit dialing to my cell.

I am guessing that any prefix, such as 1*, can then be used as speed dial button on the 2182, right?

I would prefer a secret pwd or something be required on the 212 so nobody else can use the PSTN- should they get on the network somehow.

The second option (maybe better, or not?) is to limit it by obi device number. Can these be spoofed or cloned?

If trying to access multiple 212 from multiple Obi phones, should I setup an individual trunk on each 212 and go from there? Will that mess up my InboundCallRoute that rings multiple OBi phones?

I have never setup a trunk, though I have read about it.

Thanks!

PS- Would setting up Trusted Callers do this, with some key-programmed sequence/speed dial to get a second dial tone on the 212?

PPS- What about setting up a Voice Gateway on each 212?

Look at the 212's Call History. Does it show the call from the 2182 and if yes what number and route does the 212 then attempt?

Quote from: drgeoff on April 26, 2021, 02:38:52 AM
Look at the 212's Call History. Does it show the call from the 2182 and if yes what number and route does the 212 then attempt?

I didn't find such an animal on ObiTalk platform, but did find it on webpage access on its IP address.

The only call in Call History on 212 from yesterday is the one I did from PH1 handset as a test to confirm the line and all parts were functional. Nothing from 2182 or anywhere else.

On the 2182 there are many calls from PH1, to PP1(1*+1aaabbbcccc) and even PP1(tttwwwvvv*aaabbbcccc) where a=area code, b=exchange, c=last 4-digits and tttwwwvvv is the Obi number for the 212.

Sadly, doesn't look like anything is getting to the 212? Or is the 212 rejecting the call (would that show up in the call history?)

I wish there was a way to see a log that showed what Digitmap and/or route was used/matched?

Q: If I set the 212 LINE up as a voice gateway, it can be shared between multiple devices using secret code? The many docs I've been reading sound like it, but I don't know?

Thanks.

The following might give you a better understanding of what's happening;

Here is the format to route a call over the OBiTalk network:

<Target_OBi_Number> * <Data>

Target_OBi_number is a 9 digit OBi number
OR
A speed dial number. The speed dial points to the target OBi

To send 5551212 to OBi number 123456789:
123456789*5551212
Or
5*5551212
With speed dial#5 set to pp(123456789)

The default config uses the speed dial format.

I use a single digit for the target OBi_Number then have the digit map change it to the actual 9 digit OBi_number. You can use the following Phone DigitMap rule to validate the dialed number:
1*xx.S4
This Phone OutboundCallRoute will change the "1" to the actual OBi_Number then send the call to OBiTalk:
{<1:123456789>*(xx.):pp}

Dial 1*5551212

OBi212 OBiTalk inbound route:
{111111111>(xx.):li}

111111111 is the OBi Number of the sending device.

If you want multiple devices accessing the 212, use the same setup on those devices. Change the OBi212 to allow access by those devices:
{(111111111|222222222|333333333)>(xx.):li}

This helps a great deal, thank you.

Let me try it, and I'll give the results

I used DigitMap (8 as prefix instead of 1):

(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))

I am new to the syntax and it isn't sticking yet. Am I missing any operators or ?? I removed the < before the first 8 to match your suggestion, but not sure if I am being too literal?

So far, using the DigitMap I posted to model yours.

Dialing 8*aaabbbcccc   then hitting speakerphone

3 tones, 404 Not found

Call log on 2182 shows:

To PP1(8*+1aaabbbcccc)

This is without the change on 212 yet. And what's the deal with the system adding +1 to everything I dial?

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?

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.

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}

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?

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?

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

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

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.

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.

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

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?

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

Calling the 212 should now work.

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

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

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)

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?

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

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?

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?)

Does dialling

**9123456789*cell number

on the 2182 ring the cellphone or the 212 phone?

Quote from: drgeoff on April 26, 2021, 12:46:01 PM
Does dialling

**9123456789*cell number

on the 2182 ring the cellphone or the 212 phone?

Neither. It doesn't carry the numbers through to dial on the 212 outside line

And I'm not sure about that workaround. It doesn't seem consistent. Might be dialing too soon after reboots.

Okay, not sure why it was going to phone before, unless as I mentioned I was testing too quickly after a reboot, routes not fully functional yet and just dumped the incoming to ph.

If I dial

**123456789    by itself, add my cell after, or add * plus my cell number, they all go to 212 Line dialtone

(I removed my previous post about a possible workaround)

I can live with getting a dialtone when calling from 2182 to 212. 2-stage dialing can hide in the speed dials. But how would I then call that handset on the 212 as makeshift intercom between units?

Is this where we need to send the 8* from 2182 and have the 212 match it before sending to line? We haven't been able to make that work yet

Try setting 212's Obitalk service Inbound Direct Dialing Authentication to None and repeat the **9123456789*cell number test.

Quote from: drgeoff on April 26, 2021, 01:13:56 PM
Try setting 212's Obitalk service Inbound Direct Dialing Authentication to None and repeat the **9123456789*cell number test.

I cannot find that option on the 212

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.

Progress:

I configured the 2182 to add a Speed dial to **9123456789    where 123456789 is the obi number for the 212.

Hitting that button on the 2182 jumps to a dial tone on that outside line on the 212, which I can then dial my cell phone or other number and it connects.

I can dial with or without a leading 1 on the number. It is a GV line (FXS out from Obi202 for testing), so it doesn't care if you enter one or not.


A limitation is I can no longer contact the analog phone on the 212 using the 2182. Everything that comes in from the 2182 is dumped directly to the line of the 212, which is all ignored anyways (WHY???)

We cannot get the OutboundCallRoute of the 2182 to match up with the InboundCallRoute and associated DigitMap(s) or we could just use something like 8* to get the outside line on the 212.

This is a problem. I'm looking for suggestions. Not sure where to go from here?

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.

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.

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

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

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.

It will be a few days before I can set a test system up myself.  If you want to try the Voice Gateway method it is the last page of https://www.obitalk.com/info/documents/admin_guide/OBi-DigitMapCallRoute-Tutorial-v1-1.pdf.

I've had the Voice Gateway method working for several years between an OBi100 9 time zones away and an OBi110.  Strange that the Voice Gateway config pages on an OBi200, 202 and 1032 have the outgoing AuthUserID and AuthPassword fields but those same devices don't have the corresponding "incoming" fields on the Obitalk service pages.

Here it is: http://www.obitalk.com/forum/index.php?topic=18189.0 (http://www.obitalk.com/forum/index.php?topic=18189.0)

Posted from my other ObiTalk account

Let me know if this works for you, too

PS- That link: https://www.obitalk.com/info/documents/admin_guide/OBi-DigitMapCallRoute-Tutorial-v1-1.pdf (https://www.obitalk.com/info/documents/admin_guide/OBi-DigitMapCallRoute-Tutorial-v1-1.pdf)  was just the ticket! I adapted a more detailed guide from that tutorial. Thanks!!!

Thanks to all for all the help!