Hi Alexander, I have found the reason why these things occur. In SER sip server, if I configure ser to support NAT and in the Ringing response message to sipXtapi, ser included nat=yes to Record-Route field: Record-Route: <sip:[EMAIL PROTECTED]:5060;nat=yes;ftag=1c28742;lr=on> And sipXtapi do not process correctly as above.
If I configure ser do not support NAT and in the Ringing response message to sipxTapi do not have nat=yes in the Record-Route field: Record-Route: <sip:xxx.xxx.xxx.xxx;ftag=1c14113;lr=on> Every things will be ok! I don't know why. Have you ever tested this situation? On 6/21/07, Alexander Chemeris <[EMAIL PROTECTED]> wrote:
On 6/21/07, Phan Van Duc <[EMAIL PROTECTED]> wrote: > I have got sipxtapi source from svn (Using: svn co > http://scm.sipfoundry.org/rep/sipX/branches/sipXtapi-media-update Please, use sipXtapi branch - sipXtapi-media-update is frozen for some time, while I do not have time for video development. > sipx) and build sipxEzphone. When I am using sipxEzphone call to x-lite, > sipxEzphone continuous to send Invite message as before. I attached the log > file, can you find the errors? I see that sending messages over UDP failed, abut succeed when sending over TCP. So, problem may lay here. I'm not sure what exact is a problem, though. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
