Re: [OpenSIPS-Users] Which internal module did the hangup?

2017-03-20 Thread Bogdan-Andrei Iancu 

Hi Daniel,

That's a tricky one - mediaproxy is also using the dialog module (via 
internal API) to terminate the call. So, in both cases, the dialog 
module is doing the hangup. I guess you can spot the difference from the 
logs only :(.


Having a Reason header will make sense here.

Regards,

Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html

On 03/20/2017 03:26 PM, Daniel Zanutti wrote:

I have 2 modules that may hangup the call:
 - Dialog - duration timeout or sip ping with sip options
 - Mediaproxy - RTP timeout

On local_route, is there any way to know which module did the hangup?

Thanks




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Which internal module did the hangup?

2017-03-20 Thread Daniel Zanutti 
I have 2 modules that may hangup the call:
 - Dialog - duration timeout or sip ping with sip options
 - Mediaproxy - RTP timeout

On local_route, is there any way to know which module did the hangup?

Thanks
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users