<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">The only thing I can think of is that perhaps you have a firewall somewhere that's blocking RTP/UDP packets coming back from the server (but not the packets that formed the SIP command and response).<br></span></blockquote></div><br><div>Thanks, Ross.</div><div><br></div><div>Another question: what does it take to extend the sipPlayer test program to support two-way traffic? Sorry if that seems like a basic question but I didn't see an obvious way to do it, and didn't see it mentioned in the FAQ.</div><div><br></div><div>Thanks again,</div><div><br></div><div>Tom</div><div><br></div></body></html>