I want the OBi to bridge an incoming call on SP2 out on SP1.
I have Sipsorcery registered on SP2. Sipsorcery can spoof a CallerID, so I'm placing the number I want the incoming call routed to in the CallerID. I don't want all incoming calls on SP2 bridged, so I prefix the CallerID with a "9" and strip it off when I make the call. I'm testing with Cox Communications' number 623-594-1000, so I'm setting the CallerID of the SP2 inbound call to "96235941000".
My 1st test OBi config:
SP2 X_InBoundCallRoute: {9xxxxxxxxxx:sp1($1)},{ph}
ITSPA DigitMap: (1[2-9]xxxxxxxxx|[2-9]xxxxxxxxx|<480>xxxxxxx|<9:>[2-9]xxxxxxxxx)
I did not get a match on my InboundCallRoute and the OBI phone port rang.
My 2nd test OBI config:
SP2 X_InBoundCallRoute: {96235941000:sp1($1)},{ph}
ITSP A DigitMap: (1[2-9]xxxxxxxxx|[2-9]xxxxxxxxx|<480>xxxxxxx|<9:>[2-9]xxxxxxxxx)
By hard coding the whole number I got a match on the InboundCallRoute, but the ITSPA DigitMap did not strip off the leading "9" and tried to call 9-623-594-1000 on SP1.
My 3rd test OBI config:
SP2 X_InBoundCallRoute: {6235941000:sp1($1)},{ph}
ITSP A DigitMap: (1[2-9]xxxxxxxxx|[2-9]xxxxxxxxx|<480>xxxxxxx|<9:>[2-9]xxxxxxxxx)
I set the Inbound SP2 CallerID to "6235941000" and the call was bridged successfully.
I have 2 problems.
(1) Sp2 InboundCallRoute seems to not recognize x's.
(2) My ITSPA DigitMap is not stripping the leading "9".
Is my logic correct in my 1st test config? Do I strip the leading "9" in the DigitMap or the InBoundCallRoute? I'm so confused!
Any help will be appreciated.
Update:
I'm on the current software version 1.1.0 (build:1892)