Call out line port obi110#2 when calling from phone port on obihai#1

<< < (2/4) > >>

magamaga:
What I see it doing is ....it's appending the local area code and it's calling 1-localareacode-7digitnumberdialed via the sp1 interface which is the default on obihai #1.


Here are the digimaps and outbound call routes:

obihai#1

Phone port

Digimap

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

OutboundCallRoute

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

obihai #2

obitalk service

Digimap

(<ob>xxxxxxxxx|obxxxxxxxxx)

InboundCallRoute

{200111111>(088xxxxxxx|xxxxxxx):li},{(200222222|200111111)>(xx.):SP1},{(200222222|200111111):aa},{ph}

azrobert:
In the Phone DigitMap why are you using |088*******|******* instead of |088xxxxxxx|xxxxxxx
Are you only routing specific numbers to OBi110#2?

Phone OutboundCallRoute you are missing 088xxxxxxx

In Service -> ITSP Profile A General -> DigitMap
You must have a rule like this: <1localareacode>xxxxxxx
Remove It.

If you are routing just specific numbers to OBi110#2 and want to keep 7 digit dialing for SP1, it can be done.

magamaga:
My apologies.   I have corrected the *'s and placed x's instead. 

I want all 7 digit dialing at obi#1 to go out the line port on obi#2.   I dont ever dial 7digit numbers out SP1 on obi#1.

I removed the "localarea" part from the  ITSP Profile A General -> DigitMap on obi#1

I'm now getting a "The number you dialed was rejected by the service provider Reason is 404"

Seven digit calls from obi#2 is working fine and they only go out on port "Line" which is the default one.





Here is the config again:

Obi#1:

Phone Port
Digimap: 

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

Outboundcallroute:

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

 ITSP Profile A General -> DigitMap:

(*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)

Obi#2:

Obitalk Service:
Digimap:

(<ob>xxxxxxxxx|obxxxxxxxxx)

InboundCallRoute:

{200111111>(088xxxxxxx|xxxxxxx):li},{(200111111)>(xx.):SP1},{(200111111):aa},{ph}

 ITSP Profile A General -> DigitMap

(*xx|1xxxxxxxxxx|<1localareacode>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)


Here is the status of the call on obi#1

Number of Active Calls: 1
Call 1             
Terminal 1                      Terminal 2
Terminal ID       PHONE1       Announcement1
State              connected    connected
Peer Name      
Peer Number   2770658   
Start Time        10:29:43    10:29:43
Duration        00:00:01    00:00:01
Direction        Outbound    Inbound

magamaga:
So it looks like obi#2 is rejecting the call.  I was able to capture this happening before going to the announcement with the error :

Number of Active Calls: 1
Call 1             

Terminal 1                            Terminal 2
Terminal ID         PHONE1         OBiTALK1
State                 trying            lookup
Peer Name      
Peer Number   2770658   200222222*2770658
Start Time          10:54:22            10:54:22
Duration          00:00:00   00:00:00
Direction   Outbound   Outbound
Peer RTP Address      0.0.0.0:0
Local RTP Address      192.168.2.13:43988
RTP Transport      UDP
Audio Codec      tx=; rx=
RTP Packetization (ms)      tx=0; rx=0
RTP Packet Count      tx=0; rx=0
RTP Byte Count      tx=0; rx=0

magamaga:
Sorry again.   I had one wrong digit in obi#2's ob number on the ouboundcallroute in obi#1.  I've corrected it and it now places the call, but it is ringing the phone port on obi#2 instead of routing to the line port.

Navigation

[0] Message Index

[#] Next page

[*] Previous page