Not a Valid Number Msg

(1/3) > >>

NerdUno:
I was using an experimental version and wanted to take advantage of the new features in the latest firmware. Had to load the update manually. After update, outbound calls work fine. But calling in from a number in circle of trust, then pressing 1 to connect call yields "This is not a valid number" and hangup. Any idea how to fix Humpty?

obi-support2:
AA Option 1 tells the AA to call the number as specified in the AA parameter NumberOnNoInput, which by default is "0". This is the same number the AA will call when you don't enter any option after the AA announces the menu 2-3 times.  Note also that the default AA OutboundCallRoute is to ring the PHONE port when 0 is called (see the rule {0:ph} there).

It could be that your AA DigitMap does not contain a  "0|" rule, hence the AA complaint about an invalid number. You can modify the NumberOnNoInput parameter to other number that you desire, but make sure to
also add a corresponding rule in AA's OutboundCallRoute to let AA know where to send that
number to.

NerdUno:
Could you post what the default AA DigitMap and OutboundCallRoute should be? I haven't changed these, but I don't see the entries you mentioned. Thanks.

NerdUno:
Figured it out. Unless AutoProvisioning is Disabled, the new setup from HQ wipes out the {0:ph} entry in AA OutboundCallRoute. Not sure why, but now it works again. This wasn't a problem until the latest firmware update if that helps find what caused the problem.

MichiganTelephone:
Quote from: NerdUno on February 22, 2011, 05:31:51 am

Could you post what the default AA DigitMap and OutboundCallRoute should be? I haven't changed these, but I don't see the entries you mentioned. Thanks.


On my OBi110 under "Auto Attendant", I see the following (both have the "Default" checkbox checked, although I had to temporarily uncheck them to be able to copy and paste the strings here):

DigitMap:
Code:

([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))

OutboundCallRoute:
Code:

{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}

I did upgrade to the new firmware, so I'm not sure why yours got changed and mine didn't, although I am not using auto-provisioning.  So maybe it's something in the OBiTALK portal rather than the firmware that's causing the problem, or maybe it only occurs only if you have auto-provisioning enabled and you get the new firmware.

Navigation

[0] Message Index

[#] Next page