Normally, rtpproxy will reuse the ports and then it is normal to see the packets coming from the PSTN GW to the same port. As Maxim mentioned, it would be helpful to perform a tcpdump on all interfaces for both SIP and rtp/udptl traffic and post it somewhere.
Regards, Ovidiu Sas On Thu, Oct 23, 2008 at 6:47 PM, Maxim Sobolev <[EMAIL PROTECTED]> wrote: > Ronald Voermans wrote: >> Dear list, >> >> Our company is using RTP Proxy in combination with OpenSer 1.3. We are using >> RTPProxy in bridge mode. I have the following issue: >> >> A faxcall comes in via OpenSer, and is correctly proxied to the client. >> RTPProxy also works correctly. Next, the PSTN Gateway sends a Re-INVITE to >> check if the client supports T.38 (with SDP). The client responds with '488 >> Not Acceptable here', so the PSTN Gateway sends another (RE)-INVITE with >> alaw as the preferred codec. However, with this second re-invite a *new* >> RTPProxy-session is made. Is this because there was a 488 reply instead of a >> 200 OK (with SDP) reply? >> >> For some reason (which I don't know at the moment) the client responds with >> an OK which is then forwarded to the PSTN Gateway, which is then again >> ACKed. However, the PSTN Gateway keeps sending its RTP to the initial port, >> instead of the port for the *new* RTPProxy-session. >> >> Ultimately this ends up in disconnecting the call. >> >> Does anybody know what could be the cause of this, and (more important) how >> to solve this? > > Ronald, > > It would help a lot to debug an issue if you can include SIP packet > capture into your problem report. > > Thanks! > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > _______________________________________________ > Users mailing list > Users@rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
