Auto Attendant on Obi110 does not pick up

[vbprof]

I have Obi110 and obi202, and both are registered in my account.  I use phone port on Obi110 to dial obi202 directly (**9 obi202number), the auto attendant picks up, but if I use phone port1 on obi202 to dial obi110 directly (**9 obi110number), the auto attendant does not pick up.  Instead, the phone port rings.  This is very strange.  Does anyone know what I did wrong?

By the way, everything else works fine.  If I call into obi110 (e.g., my cell to service provider1 on obi110) with my trusted number, the auto attendant picks up fine.

[azrobert]

You can manually define this using OBi Expert.
Go to Voice Services -> OBiTalk Service
Add the following to the beginning of the OBi110 InboundCallRoute:
{510123456:aa},

Change 510123456 to the OBi number of your OBi202.
If your current InboundCallRoute is ph use the following:
{510123456:aa},{ph}

There should be speed dials automatically defined to call the other OBi, so you don't need to dial **9.....
If you don't have speed dials, define one like: pp(510123456)

[vbprof]

Thanks for the reply.  This is the current value at Voice Service -> ObiTalk Service->InBoundCallRoute:

{(290129511|500612811)>(xx.):SP1},{(290129511|500612811):aa},{ph}

where 290129511 is my Obi softphone and 500612811 is my Obi202.  I am new and not sure what ">(xx.):SP1" part means, but it seems to me that Auto Attendant should pick up when Obi202 (500612811) calls?  

Also, the similar setting is at my Obi202 InBoundCallRoute, and it was working fine.  There is something I am missing here about this Obi110.

[azrobert]

The 2nd rule looks good and should route the call to the AA. In the past there was an OBi number bug. I don't remember if it was the receiving OBi not recognizing the OBi number or the sending OBi transmitting a wrong number. Check the OBi100 call history to verify this. The OBi number should be next to Peer Number.

To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column then click Call History.

If you are not getting the correct OBi number, I suggest upgrading the firmware on both OBi's. Be aware that GV is defined differently with the newer firmware and will have to be redefined if you are currently using the old method. You could also change {ph} to {aa} but now all OBiTalk calls will be routed to the AA.

You can route an outbound call to a trunk on another OBi via OBiTalk. That is what the 1st rule is for. The >(xx.) is checking if you transmitted an outbound number and then routes the call to SP1. You can test this by defining a speed dial like this:
pp(200123456*18005551212)

Another way to route a call to the AA is define a speed dial like this:
pp(200123456*AA)

Then add a rule in the receiving OBi's OBiTalk InboundCallRoute to check for the literal "AA":
{>AA:aa}

This doesn't check for the OBi number, only the literal.

[vbprof]

I did what you suggested.  The call log from the receiving Obi110 shows:

Terminal ID   OBiTALK1   PHONE1
Peer Name      
Peer Number      
Direction   Inbound   Inbound
20:54:48   Ringing   
20:54:54   End Call   

It does not seem to have any Obi number as the inbound ID.  It must be a system error/bug (the other one shows From 'Obi110' pp1(200586211), which is the correct way).  I just started using obi devices last week, and I am sure I have the most recent firmware (it did ask me to update the Obi110 firmware when I started).

I also tried your trick to place "AA" after the speed dial (it seemed that I have to use the web page, and directly placing the pp() in ObiTalk.com did not work), and it worked well.  Thanks.  I guess this is a workaround.

Just curious, where can I find syntax for setting up the speed dial, such as syntax for making something like pp(200123456*18005551212)?  Thanks again.

[azrobert]

The following is a link to the Admin Guide, but I don't know if it has an understandable explanation.
http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf

I'm not sure I understand what you want to know about syntax.
The syntax is pp(destination *data)

pp is the OBiTalk network
The destination can be an OBi number or a speed dial number defined as pp(OBi Number)
For example it can be: pp(10*123)
Speed dial 10 must be defined as pp(200123456) or **9200123456
123 is the data sent to OBi number 200123456

The receiving OBi InboundCallRoute rule:
{sending OBi# >data :dest}
The arguments are optional and if not supplied will not be used to match the incoming call.
{>AA:aa} will match any call with data "AA".
{200123456:aa} will match OBi# 200123456 with or without data.
If you want to check the data for a pattern it must be enclosed in parentheses like >(xx.)

The OBi's default is setup to send data over OBiTalk without using a speed dial.
See these rules in the Phone Port definition
DigitMap: [1-9]x?*(Mpli)
OutboundCallRoute: {([1-9]x?*(Mpli)):pp}

If you want an explanation, just ask.

You would dial the following sequence from the phone attached to the OBi phone port:
10*18005551212
10 points to speed dial# 10
Speed dial# 10 must be defined like: pp(200123456)
18005551212 is the data being sent to OBi# 200123456

I don't use OBiTalk to configure my OBi's. I use the local interface. If you use the local interface, you must disable Auto Provisioning. If Auto Provisioning is disabled you can't use OBiTalk to configure your OBi's. If you then turn on Auto Provisioning, ObiTalk will overlay any changes with defaults. There is a method to switch between the 2 methods.

I believe to add a speed dial from OBiTalk you click on Speed Dials from the dashboard then supply the speed dial number and the command. Click Save. I have done this to add speed dials to the OBi softphone.

[vbprof]

Got it.  Thanks again.