v1.4.7 Notice a problem with the Manager API not loading?

I have configured the file managers.conf and I haven’t changed anything as far as loading a module. The thing I have changed is upgrading to v1.4.7 from v1.4.6.

When I do a netstat and see if the service is running, it does not list any for port 5038.

Is there anything I might be missing as far as a security settings that would parse the managers.conf file but not open the port?

Thanks guys,

Kimberly C.

OS => Debian Etch 4.0
Asterisk => v1.4.7

/etc/asterisk/managers.conf file

; Asterisk Call Management support
;
; By default asterisk will listen on localhost only.

[general]
displaysystemname=yes
enable=yes
webenable=yes
port=5038
bindaddr=0.0.0.0
displayconnects=yes
log_manager_events=yes

; No access is allowed by default.
; To set a password, create a file in /etc/asterisk/manager.d
; use creative permission games to allow other serivces to create their own
; files
; #include “manager.d/*.conf”

[queue]
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.255
secret=[m0n!t0r]
read=system,call,log,verbose,command,agent,user
write=system,call,log,verbose,command,agent,user