IAX Calls to IVR are disconnecting


(Aspirant) #1

We have 2 FreepBX servers connected with IAX Trunks, calls are working fine both sides.

We have IVR on One of the Server, when the users from other site dialing to IVR number through IAX trunk, calls are getting error message -

Rx-Frame Retry[ No] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: NEW
Timestamp: 00355ms SCall: 11620 DCall: 00000 10.9*.14*.5:4569]
VERSION : 2
CALLED NUMBER : 383
CODEC_PREFS : (ulaw|alaw)
CALLING NUMBER : 1448474
CALLING PRESNTN : 0
CALLING TYPEOFN : 0
CALLING TRANSIT : 0
CALLING NAME : AVAILABLE EXTENSION
LANGUAGE : en
FORMAT : 4
FORMAT2 : ulaw
CAPABILITY : 12
CAPABILITY2 : unknown
ADSICPE : 2
DATE TIME : 2020-01-28 10:07:54
CALLTOKEN : 51 bytes

-- Accepting UNAUTHENTICATED call from 10.9*.14*.5:
   > requested format = ulaw,
   > requested prefs = (ulaw|alaw),
   > actual format = alaw,
   > host prefs = (alaw|ulaw),
   > priority = mine

Tx-Frame Retry[000] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: ACCEPT
Timestamp: 00017ms SCall: 06876 DCall: 11620 [10.9*.14*.5:4569]
FORMAT : 8
FORMAT2 : alaw

Rx-Frame Retry[ No] – OSeqno: 001 ISeqno: 001 Type: IAX Subclass: ACK
Timestamp: 00017ms SCall: 11620 DCall: 06876 [10.9*.14*.5:4569]
– Executing [383@from-internal:1] ResetCDR(“IAX2/CORK-6876”, “”) in new stack
– Executing [383@from-internal:2] NoCDR(“IAX2/MTSCORK-6876”, “”) in new stack
– Executing [383@from-internal:3] Progress(“IAX2/MTSCORK-6876”, “”) in new stack
Tx-Frame Retry[000] – OSeqno: 001 ISeqno: 001 Type: CONTROL Subclass: PROGRES
Timestamp: 00368ms SCall: 06876 DCall: 11620 [10.9*.14*.5:4569]
– Executing [383@from-internal:4] Wait(“IAX2/MTSCORK-6876”, “1”) in new stack
Tx-Frame Retry[000] – OSeqno: 002 ISeqno: 001 Type: VOICE Subclass: 8
Timestamp: 00368ms SCall: 06876 DCall: 11620 [10.9*.14*.5:4569]
Rx-Frame Retry[ No] – OSeqno: 001 ISeqno: 001 Type: IAX Subclass: ACK
Timestamp: 00003ms SCall: 11660 DCall: 00001 [10.9.18.5:4569]
Rx-Frame Retry[ No] – OSeqno: 001 ISeqno: 002 Type: IAX Subclass: ACK
Timestamp: 00368ms SCall: 11620 DCall: 06876 10.9*.14*.5:4569]
Rx-Frame Retry[ No] – OSeqno: 001 ISeqno: 003 Type: IAX Subclass: ACK
Timestamp: 00368ms SCall: 11620 DCall: 06876 [10.9*.14*.5:4569]
– Executing [383@from-internal:5] Progress(“IAX2/MTSCORK-6876”, “”) in new stack
Tx-Frame Retry[000] – OSeqno: 003 ISeqno: 001 Type: CONTROL Subclass: PROGRES
Timestamp: 01351ms SCall: 06876 DCall: 11620 [10.9*.14*.5:4569]
Executing [383@from-internal:6] Playback(“IAX2/CORK-6876”, “silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer”) in new stack
– <IAX2/MTSCORK-6876> Playing ‘silence/1.alaw’ (language ‘en’)
Tx-Frame Retry[000] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00019ms SCall: 04686 DCall: 00000 [*0.9.10.5:4569]

Rx-Frame Retry[ No] – OSeqno: 001 ISeqno: 004 Type: IAX Subclass: ACK
Timestamp: 01351ms SCall: 11620 DCall: 06876 [10.9*.14*.5:4569]
Rx-Frame Retry[ No] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG
Timestamp: 00019ms SCall: 00001 DCall: 04686 [10.9.10.5:4569]
Tx-Frame Retry[-01] – OSeqno: 001 ISeqno: 001 Type: IAX Subclass: ACK
Timestamp: 00019ms SCall: 04686 DCall: 00001 [10.9*.10.5:4569]
– <IAX2/MTSCORK-6876> Playing ‘cannot-complete-as-dialed.alaw’ (language ‘en’)
Rx-Frame Retry[ No] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00007ms SCall: 07046 DCall: 00000 [10.
.122.*:4569]


#2

“call cannot be completed as dialed” message indicates that there are no matches against any outbound route.


(Aspirant) #3

The debug I post is from the receiving server, same server receiving the calls to main line number through service provider able to hear the welcome message.

My call flow is this way, here in the First Server have IVR. IAX Normal calls are working fine both sides. I have created a new SIP trunk also, but have same issue.

image


#4

Did this ever work before? Have you defined the route for the iax trunk as intra-company?


(Aspirant) #5

context=from-internal

I am not the one implemented this and users are not sure either it worked before or not.


(Tom Ray) #6

There is also the fact that IVRs do not have a dialable extension attach to them. So while you are dialing 383 from PBX A, where does PBX B have 383 setup to route to the IVR? It would need some sort of Misc. Destination to map the digits 383 to the IVR.

Again, you cannot dial an IVR you can only be routed to it. So you need to make 383 route to it on PBX B.


(Aspirant) #7

An inbound route is there, is that fine?


(Tom Ray) #8

No because you’re using “from-internal” and Inbound Routes are not used in that context. So if you’re going to use Inbound Routes then you need to treat the trunk like the call is coming from the PSTN and not an internal system.


(Aspirant) #9

I have created a Misc Destination and Application and pointed to IVR. It’s working now.

Thanks for your help !!!