Open premkumarramasamy opened 10 months ago
Hello!
I think that our case is also related to this issue; when we enable 100rel
on the external profile (port 5080), the 486 Busy Here status is not forwarded to the internal profile. When we turn off 100rel
, everything works as it should.
In the trace screenshot, the internal FS leg is on port 5060, and the external leg is on port 5080.
Describe the bug I am facing one issue with option enable-100rel option(we have enabled this in external profile). When this option is enabled FS is not generating CHANNAL_HANGUP event. Scenario is like this: Call is established from FreeSWITCH and it is declined by the device, we are getting 486 response from the device, upon this FS is not generating CHANNEL_HANGUP event. Is there any open issue with this behaviour or am I missing some config? Without this option FS is generating the events.
To Reproduce Steps to reproduce the behavior:
enable-100rel
flag enabled in the dialplan.Expected behavior CHANNEL_HANGUP event should be sent to event socket client registered
Package version or git hash
Trace logs Provide freeswitch logs w/ DEBUG and UUID logging enabled Seeing the below message in the debug logs.
backtrace from core file If applicable, provide the full backtrace from the core file.