BYE is sent to the address in the Contact header of the INVITE. When a client is behind NAT that can mean the client gives an incorrect address (its internal not external IP which isn't reachable). In this case I assume there's some carrier NAT happening. If the client has STUN support that can work around it, or you can use one of the NDLB options - try NDLB-connectile-dysfunction On 18 April 2014 04:53, Jimmy Chang <chang33.tw@gmail.com> wrote:
Hi,
We have two different SIP Clients and they all use 3G to connect to FS. SIP_Client1 receives BYE without problem but SIP_Client2 couldn't. In the SIP_Client2 case, I don't understand why FS sended BYE to 100.77.163.183 rather than 42.71.215.54. Here are the snippet of FS log.
http://pastebin.freeswitch.org/22430
Thanks. Jimmy
--- 由於 avast! 防毒軟體已開啟防護，所以此封電子郵件將不受病毒及惡意軟體的侵害。 http://www.avast.com
_________________________________________________________________________ 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