I have been trying out several stun servers with Asterisk 1.6.0.9 and 1.6.1.0 and I keep getting the following message: [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: stun failed No matter which STUN server I point to I get those messages. Am I missing some other setting? -- Telecomunicaciones Abiertas de M?xico S.A. de C.V. Carlos Ch?vez Prats Director de Tecnolog?a +52-55-91169161 ext 2001 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090526/d28aed4c/attachment.pgp
> [May 26 12:26:35] WARNING[16174]: chan_sip.c:2695 ast_sip_ouraddrfor: > stun failed > > ? ? ? ?No matter which STUN server I point to I get those messages. ?Am I > missing some other setting?Hey Carlos, That just means the stun request failed, there are several reasons for that, I won't even try to guess. So, first try this on the Asterisk CLI: "stun set debug on" That should give you (and us) more information to troubleshoot why the stun request failed (also enable debug and verbosity as usual). -- Moises Silva Software Developer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy at sangoma.com