asterisk users - Feb 2012 - No valid transports available, falling back to 'udp'.

Hi All,

I just installed Asterisk 10.1.1 and on sip reload I see the following two
errors.

WARNING[3665]: chan_sip.c:29242 reload_config: No valid transports available,
falling back to 'udp'.
  == Using SIP CoS mark 4
WARNING[3665]: chan_sip.c:27839 build_peer: 'tcp' is not a valid
transport type when tcpenabled=no. If no other is specified, the defaults from
general will be used.

I don't understand this as I have in sip.conf
udpbindaddr=0.0.0.0

I've also tried
udpbindaddr=192.168.13.7
and
udpbindaddr=192.168.13.7:5060

with the same results.

Is there another setting that I am missing.  I have not made any changes to the
default file settings, well none that I remember.

Regards
David Klaverstyn
Systems Engineer
Information Services, Asia-Pacific
Intergraph Corporation
270 Gladstone Road
Dutton Park, QLD 4102 AU
P 61.7.3510.8951 F 61.7.3510.8980
david.klaverstyn at intergraph.com<mailto:david.klaverstyn at
intergraph.com>, www.intergraph.com.au<http://www.intergraph.com.au>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20120213/eb228846/attachment.htm>

I'm experiencing the same situation. However my sip devices and peers are
working fine

On Sun, Feb 12, 2012 at 7:02 PM, Klaverstyn, David C <
David.Klaverstyn at intergraph.com> wrote:
>  Hi All,****
>
> ** **
>
> I just installed Asterisk 10.1.1 and on sip reload I see the following two
> errors.****
>
> ** **
>
> WARNING[3665]: chan_sip.c:29242 reload_config: No valid transports
> available, falling back to 'udp'.****
>
>   == Using SIP CoS mark 4****
>
> WARNING[3665]: chan_sip.c:27839 build_peer: 'tcp' is not a valid
transport
> type when tcpenabled=no. If no other is specified, the defaults from
> general will be used.****
>
> ** **
>
> I don?t understand this as I have in sip.conf****
>
> udpbindaddr=0.0.0.0****
>
> ** **
>
> I?ve also tried****
>
> udpbindaddr=192.168.13.7****
>
> and****
>
> udpbindaddr=192.168.13.7:5060****
>
> ** **
>
> with the same results.****
>
> ** **
>
> Is there another setting that I am missing.  I have not made any changes
> to the default file settings, well none that I remember.****
>
> ** **
>
> Regards****
>
> *David Klaverstyn*
> Systems Engineer
> Information Services, Asia-Pacific
> Intergraph Corporation
> 270 Gladstone Road
> Dutton Park, QLD 4102 AU
> *P* 61.7.3510.8951 *F* 61.7.3510.8980
> david.klaverstyn at intergraph.com, www.intergraph.com.au****
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20120212/5187ea50/attachment.htm>

----- Original Message -----
> From: "David C Klaverstyn" <David.Klaverstyn at
intergraph.com>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
> <asterisk-users at lists.digium.com>
> Sent: Sunday, February 12, 2012 7:02:15 PM
> Subject: [asterisk-users] No valid transports available, falling back
> to 'udp'.
> Hi All,
> I just installed Asterisk 10.1.1 and on sip reload I see the
> following two errors.
> WARNING[3665]: chan_sip.c:29242 reload_config: No valid transports
> available, falling back to 'udp'.
> == Using SIP CoS mark 4
> WARNING[3665]: chan_sip.c:27839 build_peer: 'tcp' is not a valid
> transport type when tcpenabled=no. If no other is specified, the
> defaults from general will be used.
> I don?t understand this as I have in sip.conf
> udpbindaddr=0.0.0.0
> I?ve also tried
> udpbindaddr=192.168.13.7
> and
> udpbindaddr=192.168.13.7:5060
> with the same results.
> Is there another setting that I am missing. I have not made any
> changes to the default file settings, well none that I remember.
This WARNING message is letting you know that TCP is not available as a
transport. So, it is falling back to UDP as the transport. Unless you are trying
to use TCP, it is a harmless message.

The message should probably be changed or only displayed when a particular
setting is enabled since, as it is, it is a bit misleading. If you don't
care to use TCP and have it disabled in the configuration file, you
shouldn't be alerted to the fact that Asterisk is unable to use TCP.

Feel free to open up an issue as Paul directed in his prior message. 

Regards, 

Michael Young 
(elguero) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20120213/a7169326/attachment.htm>