News:

The OBiTALK service has reached it's End of Life period and will be decommissioned as of October 31st, 2024. More information can be found at this link https://support.hp.com/us-en/document/ish_10969583-11049883-16

Main Menu

Issue with obion outbound calls

Started by Riyas, April 02, 2012, 02:27:09 AM

Previous topic - Next topic

Riyas

Hi,

I have an issue with Obion outbound calls. I have 1 Obi110 and Obion on my iphone. All my calls are working great from my phone port (check my line port settings). But my calls from Obian is not working properly. If I dial a number starting with 06xxxxxxxx, the call is routed properly through the line port. But If I dial a number starting with 01xxxxxxxx, the call is still routed through the line port instead of "tg1". My landline is dialling **0101xxxxxxxx

I am sure that I've misconfigured something. Please find below my settings:

Line port Digitmap:
(0[6-8]xxxxxxxx|<**01>0[1-5,9]xxxxxxxx|<**3>0091[7-9]xxxxxxxxx|<**3>0097xx.|<**1>00659xx.|xx.)

Voice Services -> OBiTALK Service -> InboundCallRoute:
{(Mcot)>(Mli):li},{(Mcot)>(<*1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)):sp2},{(Mcot)>(<*3:>(Mvg3)):vg3},{(Mcot)>(<*8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)):pp},{(<*01:>(Mtg1)):tg1},{(<*02:>(Mtg2)):tg2},{(<*03:>(Mtg3)):tg3},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(<**01:>(Mtg1)):tg1},{(<**02:>(Mtg2)):tg2},{(<**03:>(Mtg3)):tg3},{(Mcot):aa},{ph}

Auto Attendant -> Digitmap:
([1-9]x?*@@.|[1-9]|[1-9][0-9]|<00:$1>|0|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**4(Mvg4)|**8(Mli)|**9(Mpp)|(Mpli)|**01(Mtg1)|**02(Mtg2)|**03(Mtg3))

Auto Attendant -> Outbound call route: {([1-9]x?*@@.):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(<**01:>(Mtg1)):tg1},{(<**02:>(Mtg2)):tg2},{(<**03:>(Mtg3)):tg3},{(Mpli):pli}

Phone port -> digitmap:
{([1-9]x?*@@.):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(<**01:>(Mtg1)):tg1},{(<**02:>(Mtg2)):tg2},{(<**03:>(Mtg3)):tg3},{(Mpli):pli}

Phone port -> Outbound call route:
{([1-9]x?*@@.):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**4:>(Mvg4)):vg4},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(<**01:>(Mtg1)):tg1},{(<**02:>(Mtg2)):tg2},{(<**03:>(Mtg3)):tg3},{(Mpli):pli}

COT settings : (Obi110 number|Obion number)

Thanks for your help.

RonR

Quote from: Riyas on April 02, 2012, 02:27:09 AM
Line port Digitmap:
(0[6-8]xxxxxxxx|<**01>0[1-5,9]xxxxxxxx|<**3>0091[7-9]xxxxxxxxx|<**3>0097xx.|<**1>00659xx.|xx.)

The technique of having certain calling patterns redirected to a different trunk by prepending a service route access code in the PrimaryLine DigitMap only works for calls made from the PHONE Port and Auto Attendant.  This is because these calls involve a two-step process:

Step 1.  Process the dialed number through the PHONE Port/Auto Attendant DigitMap, possibly transforming the original number (for example, prepending a service route access code).

Step 2. Process the number resulting from Step 1 through the PHONE Port/Auto Attendant OutboundCallRoute.

In the case of calls arriving via an InboundCallRoute, the PHONE Port/Auto Attendant DigitMap and OutboundCallRoute are not used and there is no PrimaryLine.  Call routing is the total responsibility of the InboundCallRoute rules.  Transformations made by an individually referenced DigitMap (for example, Mli) in support of PHONE Port/Auto Attendant routing may or may not be beneficial to the InboundCallRoute processing.

In other words, each InboundCallRoute rule must stand on its own with no reliance on how dialing from the PHONE Port/Auto Attendant behaves.  Each rule of an InboundCallRoute processes the originally received call information.  There is no memory of any transformation that may have occurred in a previous rule.

Consequently, to accomplish the goals of your LINE Port DigitMap in an InboundCallRoute would require:

{(Mcot)>(0[6-8]xxxxxxxx):li},{(Mcot)>(0[1-5,9]xxxxxxxx):tg1},
{(Mcot)>(0091[7-9]xxxxxxxxx|0097xx.):vg3},{(Mcot)>(00659xx.|xx.):sp1},...

Riyas

Quote from: RonR on April 02, 2012, 09:45:26 AM
Consequently, to accomplish the goals of your LINE Port DigitMap in an InboundCallRoute would require:

{(Mcot)>(0[6-8]xxxxxxxx):li},{(Mcot)>(0[1-5,9]xxxxxxxx):tg1},
{(Mcot)>(0091[7-9]xxxxxxxxx|0097xx.):vg3},{(Mcot)>(00659xx.|xx.):sp1},...


Thanks RonR for your help. I've changed the settings. Everything is working fine, except calls to 01xxxxxxxx.

I have an error message : End Call (403 Wrong login or password).

Login and password are good. because if I call from my phone port, it's working.

If I change the configuration to {(Mcot)>(0[1-9]xxxxxxxx):li}, everything works fine.

RonR

'403 Wrong login or password' is likely coming from a service provider.  Not knowing how you have TG1 configured, it's hard to speculate from there.

Riyas

Quote from: RonR on April 02, 2012, 11:01:33 AM
'403 Wrong login or password' is likely coming from a service provider.  Not knowing how you have TG1 configured, it's hard to speculate from there.


My tg1 trunk list is : sp2,li1
Digitmap: (0[1-5,9]xxxxxxxx)

It's strange that tg1 is working properly from phone port. I don't have this error message.

It doesn't really matter. I am gonna use my line port for these calls.

Thanks again for your help

RonR

Do you happen to have?:

Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : (checked)

Riyas

Quote from: RonR on April 02, 2012, 11:16:09 AM
Do you happen to have?:

Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : (checked)


Yes

RonR

Quote from: Riyas on April 02, 2012, 11:21:12 AM
Quote from: RonR on April 02, 2012, 11:16:09 AM
Do you happen to have?:

Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : (checked)


Yes

See if turning it off eliminates the '403 Wrong login or password' error.

Riyas

You know what ? it works  :)

You are great man. Thanks

RonR

X_SpoofCallerID causes the OBi to modify the SIP 'From' header to that of the incoming CallerID.  This does not occur in the case of calls from the PHONE Port or Auto Attendant.  Many (most?) service providers do not allow the 'From' header to be changed and return an error when an attempt is made to do so.

Riyas

I understand now. Thanks for your patience and explanation. :)