Do you see any entries in the FS logs relating to rtp auto-adjust at about the time the audio starts working?
If so that could indicate FS is getting an incorrect (internal) IP in the SDP from the client, and audio is starting when the client starts sending to FS after a few seconds.
The other party have to hung up, for example, in order for call to end.
This also indicates a NAT issue. The BYE hangup gets sent to the IP:port in the Contact header, not the address the INVITE came from. If the contact header is incorrect the BYE goes to the wrong place and so the client never sees it.
-Steve
On 10 December 2012 18:22, Mimiko
<vbvbrj@gmail.com> wrote:
On 10.12.2012 20:00, Steven Ayre wrote:
> So to clarify:
>
> Client -> Internet -> NAT -> FS
> works
>
> Client -> NAT -> Internet -> NAT -> FS
> does not?
>
> Since the FS NAT side appears to be working (from the 1st case), I'm
> guessing it's probably either a problem at the client side (with client
> or NAT router) or perhaps the double-NAT is causing an issue. Personally
> I haven't run FS behind NAT, so it's not a situation I've had to handle.
Thank you for a comprehensive response.
What I've seen now. Audio actually comes up, but it is taking a while.
Sometimes is ~5sec, sometimes more, sometimes never. Also, sip commands
does not take action. The other party have to hung up, for example, in
order for call to end.