[Freeswitch-users] Dingaling: using a hostname instead of stun for rtp

[Mark Campbell-Smith]

Thanks for the response Mike and Brian.

Using stun is not a problem and I have it working okay now.  Is there
something different in the implementation of the stun lookup between
dingaling and sofia?

I normally use stun.freeswitch.org and sofia never had a problem.

It doesn't matter which stun server I use with dingaling (I have tried
with numerous servers) and the same thing seems to happen.  The first
stun lookup fails with a timeout (on the first inbound call), and then
if another dingaling call is tried directly, the second stun lookup
works.

I noticed a similar behaviour by issuing the stun command from fs_cli

Thanks

On Sun, Oct 18, 2009 at 8:04 AM, Michael Jerris <mike at jerris.com> wrote:
> If you don't have working stun, jingle is not going to work very
> well.  It is a required part of the protocol.  You need to be able to
> determine your external ports for media on each call, using a host
> name will not do this for you.
>
> Mike
>
>
> On Oct 16, 2009, at 10:48 AM, Brian West wrote:
>
>> If you setup your own stun server it wouldn't do that....  But the
>> hostlookup only solves half the problem .. getting the external IP vs
>> poking holes for RTP which is what stun will do.
>>
>> /b
>>
>> On Oct 15, 2009, at 10:35 PM, Mark Campbell-Smith wrote:
>>
>>> Thanks Brian.  Is this something that is planned to be implemented?
>>> The workaround is to set the stun server also in the dingaling
>>> configuration, but as I said, for some reason the stun times for me
>>> out occasionally with dingaling.
>>>
>>> Thanks!
>>
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>