News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

outbound routing for 911 and Int'l call via line port and other via GV on SP1

Started by gv2012, February 09, 2012, 07:04:11 PM

Previous topic - Next topic

gv2012

I am looking for configuration that would route 911 and 01191 and 01197 calls via line port on my OBiTalk 110 device. All other call would use SP1.

Assistance is much appreciated ... Thx

RonR

911 calls are routed to the LINE Port by default.

Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

Physical Interfaces -> LINE Port -> DigitMap : ([2-9]11|[2-9]xxxxxx|1xxxxxxxxxx|011xx.)

Service Providers -> ITSP Profile A -> General -> DigiMap:

(<**8>01191xx.|<**8>01197xx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|
(Mipd)|[^*#]@@.'@'@@.)

where aaa is your local area code.

gv2012

RonR,

Thanks for quick response and configuration.

with following change in: Service Providers -> ITSP Profile A -> General -> DigiMap:

(<**8>01191xx.|<**8>01197xx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|
(Mipd)|[^*#]@@.'@'@@.)

I would like to understand - what happens with call other than 01191 and 01197 ... and I suspect **8 provides override dialing via SP1 service for 01191 and 01197 call, but would like to confirm.

RonR

Numbers beginning with 01191 and 01197 have **8 prepended, redirecting them to the LINE Port.

11-digit numbers beginning with 1 go out SP1.

10-digit numbers beginning wth 2-9 have 1 prepended and go out SP1.

7-digit numbers beginning with 2-9 have 1aaa prepended and go out SP1.

Numbers beginning with 011 (other than 01191 ans 01197) go out SP1.

gv2012

Thx RonR for explanation ... one more item ... noticed that when I add # after dial sequence, selection happens quickly otherwise there is noticeable 2 second delay before device takes action.

I modified your string as below and testing this with 611 call ... dialing 611 only waits about 2 or so second, but 611# immediately bridges with line port.

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1973>[2-9]xxxxxx|<**8>01191xx.|<**8>01197xx.|<**8>[2-8]11|011xx.| (Mipd)|[^*#]@@.'@'@@.)

I suspect that OBiTalk has to wait for number sequence to be completed, but if there is complete match ... is there a way to make this quicker without # at the end of dial sequence?


RonR

The two second delay on calls through your LINE Port are proabably the result of having an xx. rule.  Use instead:

Physical Interfaces -> LINE Port -> DigitMap : ([2-9]11|[2-9]xxxxxx|1xxxxxxxxxx)

RonR

Quote from: gv2012 on February 11, 2012, 06:52:12 AM
I modified your string as below and testing this with 611 call ... dialing 611 only waits about 2 or so second, but 611# immediately bridges with line port.

(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1973>[2-9]xxxxxx|<**8>01191xx.|<**8>01197xx.|<**8>[2-8]11|011xx.| (Mipd)|[^*#]@@.'@'@@.)

In case you're not aware, 911 is not processed though the DigitMap above nor through the LINE Port DigitMap (unless you were to dial **8911).  911 is handled as a special case in the PHONE Port DigitMap and OutboundCallRoute:

Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}