InboundCallRoute Explained

<< < (2/5) > >>

pvpham:
What is this programming language ?

Is the operator ">" is a logic AND gate ?

What is the OR gate operator ?

azrobert:
Quote

What is this programming language ?
I think it's OBihai own language.

Quote

Is the operator ">" is a logic AND gate ?
No. It's a separator between test1 and test2.
It's always AND.
To specify only test2 do:
{>test2:dest}

Quote

What is the OR gate operator ?
There isn't any.
To do an OR function do:
{pvpham:sp1},{>(Msp1):sp1}

The vertical bar is the OR operator within a test.
{pvpham|azrobert>((Msp1)|12345):sp1}

pvpham:
Now my home phone won't work.

I had made a change in the  X_InboundCallRoute: to a new set to see if the Obi change the way I think it should if my understanding of the syntax is correct. I returned   X_InboundCallRoute: back to its beginning before the change. Now the home phone won't dial. I still can answer the inbound call though.

I also still can make call from my cell phone.

Before the change, when I hit the TALK on my home phone handset, the phone starts with the burst of short tone then the long tone. Now it just the long tone. What I did wrong.

Thanks

azrobert:
The X_inboundCallRoute should only affect inbound calls.

Outbound calls use the Phone Port DigitMap and OutboundCallRoute.
Also the ITSP A DigitMap is used, but since the Cell can still make calls the DigitMap should be OK.

Did you accidentally change any of the above. Check the ITSP A DigitMap and see if it's the same as what you changed it to.

Is the Phone Port DigitMap and OutboundCallRoute set to default?
If not please post them.

pvpham:
My phone control box failed( It's a Uniden with two hand set). It happened coincidentally the same time when I made change to the OBi and reboot. That made me thinking that I did something wrong. I replaced it with the spare and everything is OK now.

Navigation

[0] Message Index

[#] Next page

[*] Previous page