Hi All, I am using ESL to control the call flow. My initial call flow is as following 1. INVITE---> FS 2. 180<--------| 3. 200<--------| 4. ------------>ACK 5. *************|-------------->INVITE 6. *************|<---------------180 7. BYE------->| 8. Retransmissions of BYE 9. *************|<----------------200 OK 10. 200(bye)<---| Now Leg B remains hanging... Shouldn't FS have killed it since legA is dead. On Application I get Channel Hangup on 200 bye. leg B call is generated using bridge command with hangup_on_answer = TRUE. Regards, Vishal Sharma
hangup_after_bridge=true? I'm not sure there is a hangup_after_answer or any reason to use one.
On May 5, 2015, at 6:42 AM, Vishal Sharma <vishal.sharma@knowlarity.com> wrote:
Hi All, I am using ESL to control the call flow. My initial call flow is as following
1. INVITE---> FS 2. 180<--------| 3. 200<--------| 4. ------------>ACK 5. *************|-------------->INVITE 6. *************|<---------------180 7. BYE------->| 8. Retransmissions of BYE 9. *************|<----------------200 OK 10. 200(bye)<---|
Now Leg B remains hanging... Shouldn't FS have killed it since legA is dead.
On Application I get Channel Hangup on 200 bye. leg B call is generated using bridge command with hangup_on_answer = TRUE.
Regards, Vishal Sharma
Yes it is hangup_after_bridge... it is used because if legb hangs up ... I want call to be disconnected. .. On 5 May 2015 20:13, "Michael Jerris" <mike@jerris.com> wrote:
hangup_after_bridge=true? I'm not sure there is a hangup_after_answer or any reason to use one.
On May 5, 2015, at 6:42 AM, Vishal Sharma <vishal.sharma@knowlarity.com> wrote:
Hi All, I am using ESL to control the call flow. My initial call flow is as following
1. INVITE---> FS 2. 180<--------| 3. 200<--------| 4. ------------>ACK 5. *************|-------------->INVITE 6. *************|<---------------180 7. BYE------->| 8. Retransmissions of BYE 9. *************|<----------------200 OK 10. 200(bye)<---|
Now Leg B remains hanging... Shouldn't FS have killed it since legA is dead.
On Application I get Channel Hangup on 200 bye. leg B call is generated using bridge command with hangup_on_answer = TRUE.
Regards, Vishal Sharma
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Similar case https://freeswitch.org/jira/browse/FS-7399 On Tue, May 5, 2015 at 1:42 PM, Vishal Sharma <vishal.sharma@knowlarity.com> wrote:
Hi All, I am using ESL to control the call flow. My initial call flow is as following
1. INVITE---> FS 2. 180<--------| 3. 200<--------| 4. ------------>ACK 5. *************|-------------->INVITE 6. *************|<---------------180 7. BYE------->| 8. Retransmissions of BYE 9. *************|<----------------200 OK 10. 200(bye)<---|
Now Leg B remains hanging... Shouldn't FS have killed it since legA is dead.
On Application I get Channel Hangup on 200 bye. leg B call is generated using bridge command with hangup_on_answer = TRUE.
Regards, Vishal Sharma
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
It's a different case, I am not using TCP, On Tue, May 5, 2015 at 9:49 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
Similar case https://freeswitch.org/jira/browse/FS-7399
On Tue, May 5, 2015 at 1:42 PM, Vishal Sharma < vishal.sharma@knowlarity.com> wrote:
Hi All, I am using ESL to control the call flow. My initial call flow is as following
1. INVITE---> FS 2. 180<--------| 3. 200<--------| 4. ------------>ACK 5. *************|-------------->INVITE 6. *************|<---------------180 7. BYE------->| 8. Retransmissions of BYE 9. *************|<----------------200 OK 10. 200(bye)<---|
Now Leg B remains hanging... Shouldn't FS have killed it since legA is dead.
On Application I get Channel Hangup on 200 bye. leg B call is generated using bridge command with hangup_on_answer = TRUE.
Regards, Vishal Sharma
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Michael Jerris
-
Sergey Safarov
-
Vishal Sharma