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:
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
They all use the same core API. I suspect since our stun server is
just a cname to many public services out there you're just thinking
its dingaling related but its really not...
/b
On Oct 17, 2009, at 7:10 PM, Mark Campbell-Smith wrote:
I noticed a similar behaviour by issuing the stun
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
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!
On Wed, Oct 14, 2009 at 11:33 AM, Brian West
Hi!
I have a hostname set in vars.conf.xml for the parameters
external_rtp_ip and the external_sip_ip instead of the usual stun. I
found that stun was timing out and was causing some problems. And as
I have a hostname, it makes sense to use that instead of relying on
stun.
However, when I use
I don't think mod_dingaling will do a lookup for host: like sofia will
as it doesn't have the code for that last I checked... I could be
wrong but I don't recall it doing that.
/b
On Oct 13, 2009, at 3:02 PM, Mark Campbell-Smith wrote:
I have a hostname set in vars.conf.xml for the
