Bridged calls get stuck after 3 minutes and doesnt hangup until RTP Timeout(resolved)

All of our transfered calls get stuck in this weird limbo stage and eventually timeout from rtp after a hangup. Weird thing is it works fine if you terminate the transfer in < 3 min, but after 3 minutes it just sticks and does not terminate the call until the rtp timeout?? So confused on this.

We are originating a call from one context that does a dial to another. Here is a simplified version

[outbound-dialer-custom]
exten => s,1,NoOp(${myid})
exten => s,n,Dial(SIP/mytrunk/15555555555,45) ;try 1

[ivr-9013]
exten => s,1,NoOp(We are in Context ivr-9013)
exten => s,n,exten => s,n,Dial(SIP/mytrunk/17777777777,45) ;try 1

Using an originate of via asterisk manager

Action: originate
Channel: Local/s@outbound-dialer-custom
Exten: s
Context: ivr-9013
Priority: 1
Timeout: 120000
CallerId: 6305551234

This is the only helpful information in the log

== Spawn extension (from-trunk, , 1) exited non-zero on ‘SIP/flowroute-000003d5’
– SIP/flowroute-000003d5 Internal Gosub(transferanswer,s,1(s,1)) complete GOSUB_RETVAL=
– Channel SIP/flowroute-000003d5 joined ‘simple_bridge’ basic-bridge <37b5719a-0631-46d8-9b46-e50f9cb36b1e>
– Channel Local/s@outbound-dialer-custom-0000039a;1 joined ‘simple_bridge’ basic-bridge <37b5719a-0631-46d8-9b46-e50f9cb36b1e>
> 0x7f19a00a6f30 – Strict RTP learning complete - Locking on source address 23.29.27.59:10950

Other than that nothing is shown until the rtp timeout notice

NEW NOTE
I just changed the outgoing context to

Action: originate
Channel: SIP/mytrunk/17777777777
Exten: s
Context: ivr-9013
Priority: 1
Timeout: 120000
CallerId: 6305551234

same results, so it is not related to using local channels.

Solution was to change my sip trunks to pjsip trunks. Now it works as expected on call termination

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.