Hello Guys,
I have a voip application for iOS based on pjsip 2.3.0.
The device in question runs iOS 9.3.4 and also seem to happen on iOS 10 beta. It is connected to IPV6 wifi network created from macbook's nat64/dns64.
The client is able to register properly with our server and also has no trouble making outbound call in UDP mode ( Everything works fine in TCP ).
The trouble is with inbound call where it fails intermittently due to the following reason when responding to INVITE with 200 OK message even though it is able to send 100 TRYING successfully just before it.
I have a voip application for iOS based on pjsip 2.3.0.
The device in question runs iOS 9.3.4 and also seem to happen on iOS 10 beta. It is connected to IPV6 wifi network created from macbook's nat64/dns64.
The client is able to register properly with our server and also has no trouble making outbound call in UDP mode ( Everything works fine in TCP ).
The trouble is with inbound call where it fails intermittently due to the following reason when responding to INVITE with 200 OK message even though it is able to send 100 TRYING successfully just before it.
pjsua_core.c .... Sent: 2016-07-31T16:49:32.443 <srcipv6:port> -> <dstipv6:port> 1005 SIP/2.0 200 OK Via: SIP/2.0/UDP
--end msg--
tsx0x1401d82a8 ....Error sending Response msg 200/INVITE/cseq=95989621 (tdta0x140866000): No route to host ....Transport error, terminating transaction. Err=120065 (No route to host)pjsua_call.c .Error sending response: No route to host [status=120065] APIException: API call '::pjsua_call_answer( CALL_REFERENCE, PJSUA_SIP_RESPONSE_STATUS_OKAY, NULL, NULL )' failed with result code = 120065 ('No route to host') Note that this happens only intermittently. Once an inbound call succeeds after sending 200 OK to INVITE then the subsequent calls do succeed. The problem does not exist in IPV4 networks.
I also did a packet capture and found that there is no trace of 200 OK message in it even though pjsua_core.c's trace tells otherwise as seen above.
Sincerely welcome any inputs on how to proceed further or if there are any fixes.
Thanks,
Aravind S.
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
