Then it may not even be a bug, How are you doing this
first what methods and what not are you using to make these calls,
can you post us a sample script?
On Jun 26, 2014, at 2:46 PM, Ashou Han <ashou@mobile-sphere.com>
wrote:
Hi there,
There is a bug for Lua, that the hangup cause not updated once
originated the call.
I originated a call to my opensips proxy with a 183 back, lua
hangupCause return SUCCESS, but few seconds later the far end
carrier
return USER_BUSY (see this in the DEBUG log). But
session:hangupCause()
still return SUCCESS, not the updated cause: USER_BUSY.
FS version:
FreeSWITCH Version 1.2.22+git~20140309T154101Z~455941d369~64bit
(git
455941d 2014-03-09 15:41:01Z 64bit)
FreeSWITCH Version 1.2.23+git~20140506T190611Z~88216387e0~64bit
(git
8821638 2014-05-06 19:06:11Z 64bit)
FreeSWITCH Version 1.2.10+git~20130628T211259Z~e29731d673 (git
e29731d
2013-06-28 21:12:59Z)
All have the same bug!
Thanks,
Ashou Han
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.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