SPA2102 and OBI110

<< < (2/4) > >>

Eleventh:
RonR. The linked you gave me worked. Thanks a lot.

I have a few questions though.

I have my mobile number setup as a trusted caller on OBI's Sp1 and AA answers but when I choose option 1 to proceed with the call only the Phone line rings. but if an unknown caller calls the Sp1 it rings both the phone and the Vg5 fork.

RonR:
When you "Press 1 to continue", the Auto Attendant calls the number configured at NumberOnNoInput which defaults to 0.

0 rings the PHONE Port using the {0:ph} rule in the OutboundCallRoute.

You can't fork a call from NumberOnNoInput or the OutboundCallRoute.

Conseqently, I never figured out a way to ring VG5 in addition to the PHONE Port from the Auto Attendant.

Stewart:
Quote from: RonR on November 18, 2011, 07:05:26 pm

You can't fork a call from NumberOnNoInput or the OutboundCallRoute.  Conseqently, I never figured out a way to ring VG5 in addition to the PHONE Port from the Auto Attendant.
Could you route 0 to a VG that calls back into the OBi, e.g. points to 127.0.0.1, with a caller ID that is treated as unknown, i.e. it will fork, but will be recognized by the user as a trusted caller?  Sorry, I don't have time to test this now.

Eleventh:
I noticed something odd while dialing out on the VG5(pap2) device. The default dialout setting on OBI is the PSTN. but if I try to dial on the VG5(pap2) it connects but once the party answers it drops the call and get a busy tone. But if it try to dial **8 first it connects properly. any ideas?

RonR:
Given...

Voice Services -> SPx Service -> X_InboundCallroute:

...,{pap2>(<**8:>(Mli)):li},{pap2>(<**9:>(Mpp)):pp},{pap2>(Mli):li},{ph,vg5(pap2)}

there shouldn't be any difference.  When **8 is dialed, it should be stripped off before the call goes out the LINE Port (the first bolded rule).  Without **8, the call should still go out the LINE Port (the second bolded rule).

Navigation

[0] Message Index

[#] Next page

[*] Previous page