Joan, The E10 means that the proxy was not able to open ports for sending/receiving RTP traffic on. Can you please run the rtpproxy in foreground (-f command line switch) and post log output here. This would help a lot to diagnose the issue.
Joan wrote: > 2008/11/24 Klaus Darilion <[EMAIL PROTECTED]>: >> Hi Joan! >> >> I suggest to create an openser config with the wizard on sipwise.com. >> Then analyze this config and you will learn how to apply nat traversal >> and use rtpproxy. >> > Ok, as Klaus have suggested, I've generated the configuration (also > with the pattern to route outgoing trough PSTN), and same thing > happens ... > >>From the logs: > /usr/sbin/kamailio[8755]: Callee is not local - M=INVITE > RURI=sip:[EMAIL PROTECTED] F=sip:[EMAIL PROTECTED] > T=sip:[EMAIL PROTECTED] IP=192.168.253.12 > [EMAIL PROTECTED] > /usr/sbin/kamailio[8755]: DBG:nathelper:force_rtp_proxy2_f: proxy reply: E10 > /usr/sbin/kamailio[8755]: ERROR:nathelper:force_rtp_proxy2_f: > incorrect port 0 in reply from rtp proxy > > As I see, doesn't matter the logic I use for routing (altought the > sipwise, must be better that mine at this point), rtpproxy always > returns me a E10. Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: [EMAIL PROTECTED] Skype: SippySoft _______________________________________________ Users mailing list Users@rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users
