The management interface won't be on 5060 (well.. very unlikely). netstat -nlp|grep opensips would be more insightful. :) ie: what's opensips listening on.
According to the docs, the default port should be 8080. I'm not sure what IP it listens on. I see in the 1.6 docs that it specifically says that picking the bind interface is on the roadmap.. So not sure where it DOES listen.. The output of the netstat cmd should help you out. -Brett On Tue, Mar 30, 2010 at 9:22 AM, brianpocock <[email protected] > wrote: > > I've used: netstat -nlp | grep sip, this was the result > > udp 0 0 *.*.*.*:5060 0.0.0.0:* > 28323/opensips #PUBLIC ADDRESS > udp 0 0 192.168.1.2:5060 0.0.0.0:* > 28323/opensips #PRIVATE ADDRESS > udp 0 0 127.0.0.1:5060 0.0.0.0:* > 28323/opensips #Loopback > > its running on port 5060, I set it to use 5060 and I still get the error: > Cannot connect to OpenSIPS Server via Management Interface > (192.168.1.2/5060) > > Thanks for the help > -- > View this message in context: > http://n2.nabble.com/Control-Panel-Can-t-login-tp4817133p4824766.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
