On Wed, Feb 3, 2010 at 12:17 AM, Ben Dinnerville <[email protected]>wrote:
> > This is usually due to an error with the SIP stack not being loaded due > to an error - make sure that full logging is on and check your log file > and search for ERROR and see if there is any mention to SIP (chan_sip.o > etc), alternatively, start asterisk from the command like with asterisk > -vvvvvvvvvdddddddddc and watch the output to screen for any errors at > startup. Fix the error and SIP will start up. > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > Thank you very much for your reply . I found my mistake . It was coming from my attempt to copy the old sip.conf & extensions.conf onto the new build ones . It seems that it is not possible this way .
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
