Disabling digit map items

<< < (4/4)

OzarkEdge:
Quote from: Hi-Wire on August 10, 2015, 08:39:01 am

Hey there,

"*123" works great and "##", when typed during a call, works as well.

BUT, I'm now having problems dialing "*97" as well as "*99". Any thoughts on how to fix that?

Thanks!


Some rules to know:

o  OBi digits dialed (before establishing a call) must be mapped and routed in the OBi dial plan (digit maps and call routes) unless noted otherwise.  Typically, if you want to enable digits dialed for voice service SPn using ITSP Profilex digit map, you should map those digits in that respective digit map (Mspn).  Once a call is established, digits dialed are processed by the service provider, not by the OBi dial plan.

o  A dial plan does NOT apply to an OBi Call Forward TK(number).

o  A dial plan does NOT apply to an OBi Speed Dial TK(number) when the trunk TK() is specified. The Speed Dial 1-99 digits dialed are mapped in the PHONE port digit map (Mphn), but are not routed.

o  A dial plan does NOT apply to an OBi Voice Gateway AccessNumber TK(number).

o  OBi Star Codes are defined under the OBi web interface Star Codes and are matched automatically last by default and do NOT require dial plan support. However, precedence is given to a literal/exact match in either a digit map or call route to allow using a matching service provider feature code first (*xx is not a literal/exact match and will not disable any OBi Star Codes). A conflicting OBi Star Code can be reassigned under its Star Code Profile to still allow its use.

o  Examine the OBi Call History to confirm what digits dialed were routed to what voice service.  If no match is determined between the digits dialed and the PHONE port digit map (Mphn), the digits dialed are evaluated for a matching OBi Star Code. Otherwise, an an error message/fast busy signal is returned.

Therefore:

o  Since *12 is an OBi Star Code that matches by default, you must map *123 to override *12 and to pass *123 to Anveo.

o  You must not map ## since it is dialed during a call in progress.

o  You should map *97 and *99 to pass same to Anveo.  And this will override any same Star Codes, if defined under the active Star Code Profile.

So, your Anveo digit map should include rules |*97|*99|*123|.  And not rules |*12|##|.

Edit:  Actually, leaving ## in the dial plan for its default OBi usage should not affect dialing ## during a call in progress.

OE

Hi-Wire:
Thanks, OzarkEdge!

To be candid, roughly 96.47% of what you said was over my head. That said, I've got the following commands working:
*97
*99
*123

I did so by adding in:
|*97|*99|*123|
to my DigitMap

HOWEVER, now, when I'm on a call, pressing "##" does nothing. It is supposed to prompt me for an extension to transfer to.

Help! Any ideas on how to put this to bed?

OzarkEdge:
You said previously that dialing ## works during a call.  Now it does not?

Apparently, ## is an Anveo in-call feature for call transfer, yes?  Well, when you dial ## during a call, the OBi dial plan is not in play.  Anveo should process the digits dialed, yes?

So, ask Anveo?

OE

Navigation

[0] Message Index

[*] Previous page