> > Maya > i would make sure that you are responding with 200OK and SDP matching the incoming order. It is invalid to change the codec order. You can remove the codecs you don't support, but you can't change the order. Some UA or UAS will silently drop your 200OK and will not send/forward ACK to you. If you get incoming call with codec payload: 0 4 6 18 101, and you don't support 18 (G729), it is ok to reply with 200OK as 0 4 6 101. However, if you respond with 6 18 0 4 101 it is not valid. this is a common mistake i have seen in many implementations. I use the same platform as you, but i don't have the same problem. Therefore, i would carefully examine what you are responding. Wireshark or other traces will certainly help into troubleshooting your issue. Alex > > Message: 1 > Date: Wed, 3 Mar 2010 14:27:34 +0200 > From: Maya Zalcberg <maya@xxxxxxxxxxx> > To: pjsip at lists.pjsip.org > Subject: incoming call problem > Message-ID: > <a87a8ade1003030427x53f3155dq38f4b92f62314711 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > I am using the latest version of pjsip (1.5.5) for iPhone 3.2.1. > The codec i prefer to use is G729 (although i can also work with others, > like G711_ULAW or G711_ALAW). > It works fine when my client is initiating the call. > The problem is when my client receives an incoming call. The client gets > the > invite request and answers with 200OK. Consequently, the user that > initiated > the call thinks that the call is initiated successfully, and sends to my > client ACK (to the right port).He continues sending RTP, but my client > doesn't get the ack, and I guess still waits for the call to be confirmed > by the other side. As a result there is no voice on my client's end (even > though rtp is being sent to it's port). Obviously, the other side doesn't > get any voice either. Because my client for some reason doesn't realize he > got the ACK notification, he keeps sending 200OK to the other side. > > Thanks, > Maya > > -- > Maya Zalcberg > www.zemingo.com > 972523328356 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20100303/ed3c73bc/attachment-0001.html > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20100303/9ace008d/attachment.html>