Thank you for the suggestion, Bob.

I slimmed down my config to this, plus the sleep/playback/hangup. I confirm seeing the 180 in the signalling, no RTP, it waits a bit, then the 200 OK and RTP floods through.

I _know_ this should simply work, but... it doesn't. Anyone else got any thoughts?

Cheers again;

 - Jock

On Mon, Aug 30, 2010 at 3:20 PM, Bob Coleman <bobc@devassert.com> wrote:
I havent tried changing the ringing to something else, but I have had
success with this:

<action application="set" data="instant_ringback=true"/>
<action application="ring_ready" />

With no pre-answer. I found as soon as it pre-answered, in my
situation, that the ringing tone stopped.

On Tue, Aug 31, 2010 at 7:35 AM, Jock McKechnie
<jock.mckechnie@gmail.com> wrote:
> And I agree that it must work, somewhere. But it does not.
> Work with me here: Firstly, I tcpdumped on the FreeSWITCH machine. If I'm
> not seeing the RTP on the FS machine, it's not going to be anything like a
> firewall or a NAT issue. Secondly, and far more telling (as the above could
> be related to me screwing up the tcpdump somehow): I get the Playback audio,
> so it is possible to get audio back down the line eventually and the RTP
> does reach the caller, so RTP is able to flow from FS to caller without
> interference (as I said in the initial mail, the only RTP sent from FS
> starts _after_ the 200 OK). It simply is that FS is not sending out early
> media.
> Like I said, either I'm doing something remarkably stupid, or there is
> something extremely strange going on here.
> Should I try to use ring_ready AND pre_answer in combination? I have not
> attempted that yet. If so, in what order?
>  - JP