No call disconnect events from FreeSWITCH on outbound calls originating from FreeSWITCH

[case...@gmail.com]

Hi Everyone,

I'm trying to write an app to interface with FreeSWITCH via AMQP through the ecallmgr, and I noticed that when I send an AMQP message to originate a call to a soft phone, if I hang up from my soft phone, there is no event returned from the AMQP bus that the call was disconnected. In 'tail'ing the FreeSWITCH debug log, I can't see any indicator that FreeSWITCH recognized that the call disconnected (there's no activity when the call disconnects), though the FreeSWITCH log definitely shows that a call is disconnected when an inbound call is hung up from the caller end or when a call is disconnected by FreeSWITCH using the AMQP "hangup" request.

This is critical for my app to recognize when an outbound call originating from FreeSWITCH is disconnected from the receiving end. Is this a bug in FreeSWITCH? Is there any way to be notified when this kind of call is disconnected?

Thanks for your help!

Casey

[Darren Schreiber]

Can you attach the logs from FreeSWITCH with the SIP trace enabled please?

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[case...@gmail.com]

Hey Darren, after I applied your fix to my other post, this problem went away and I started receiving event notifications through FreeSWITCH and AMQP for outbound disconnects. I'm very glad to get this cleared up.

Thanks for your help.

Casey