isaac Posted January 2, 2009 Report Share Posted January 2, 2009 CS410 crashes whenever I press 5 to hear time/date stamp when listening to messages. This had worked before New Years.. Interestingly enough when I ssh and do a date command, I get comcerto:~# date Thu Jan 1 00:08:52 UTC 1970 I am suspecting this is the issue. Can anyone confirm and advise how to fix??? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 2, 2009 Report Share Posted January 2, 2009 CS410 crashes whenever I press 5 to hear time/date stamp when listening to messages. This had worked before New Years.. Interestingly enough when I ssh and do a date command, I get comcerto:~# date Thu Jan 1 00:08:52 UTC 1970 I am suspecting this is the issue. Can anyone confirm and advise how to fix??? What version? Crash like in process dies?? Apart from that, you should also take care about the NTP. Obviously envelope information without current time has only limited value. Quote Link to comment Share on other sites More sharing options...
hosted Posted January 2, 2009 Report Share Posted January 2, 2009 This happened alot to us on the older software. But we havnt had any problems in 6+ months. Quote Link to comment Share on other sites More sharing options...
isaac Posted January 5, 2009 Author Report Share Posted January 5, 2009 What version? Crash like in process dies?? Apart from that, you should also take care about the NTP. Obviously envelope information without current time has only limited value. We are running 2.1.0.2115 (Linux) Interestingly enough, envelope has current time but system time is different. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 5, 2009 Report Share Posted January 5, 2009 We are running 2.1.0.2115 (Linux) Interestingly enough, envelope has current time but system time is different. Oh, maybe you can upgrade to 3.1.2.3120. I would suggest you make a backup first (log in to the system and tar the /pbx directory), so that if anything should go wrong you can always move back to that version. Quote Link to comment Share on other sites More sharing options...
isaac Posted January 5, 2009 Author Report Share Posted January 5, 2009 Oh, maybe you can upgrade to 3.1.2.3120. I would suggest you make a backup first (log in to the system and tar the /pbx directory), so that if anything should go wrong you can always move back to that version. 3.1.2.3120 created many problems on inbound and outbound calling. It seems like dialplan now automatically strips 1 from NA numbers and I cannot get it to send numbers with the +1. In addition, inbound calls are not playing autoattendant file. I restored from TAR and now NO phones can register nor can I make any calls to PBX. Please help! I have 1st gen white CS410. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 5, 2009 Report Share Posted January 5, 2009 I have 1st gen white CS410. Ouch. The white edition does not have the features that you need to run version 3. Check the /etc/network/interfaces file. Make sure that there is no "eth2". Quote Link to comment Share on other sites More sharing options...
isaac Posted January 5, 2009 Author Report Share Posted January 5, 2009 Ouch. The white edition does not have the features that you need to run version 3. Check the /etc/network/interfaces file. Make sure that there is no "eth2". No eth2: #This file was automatically generated by the IP PBX. auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 70.x.x.x network 70.x.x.x netmask 255.255.255.192 broadcast 70.x.x.x gateway 70.x.x.x auto eth1 iface eth1 inet static address 1.1.1.1 network 1.1.1.0 netmask 255.255.255.0 broadcast 1.1.1.255 Log File shows: Logfile Clear or Reload the log. [1] 2009/01/05 16:31:15: Starting up version 2.1.0.2115 [8] 2009/01/05 16:31:15: Route: eth0 462a4400 ffffffc0 [8] 2009/01/05 16:31:15: Route: eth1 01010100 ffffff00 [8] 2009/01/05 16:31:15: Default Route uses 70.x.x.x [7] 2009/01/05 16:31:15: Found time zones AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET CST CAT IST GMT [1] 2009/01/05 16:31:15: Working Directory is /pbx [5] 2009/01/05 16:31:17: Starting threads [7] 2009/01/05 16:31:17: UDP: Opening socket [0] 2009/01/05 16:31:17: UDP: bind() to port 5060 failed [0] 2009/01/05 16:31:17: FATAL: Could not open UDP port 5060 for SIP [7] 2009/01/05 16:31:17: Opening TCP socket on port 5060 [7] 2009/01/05 16:31:17: Opening TCP socket on port 5061 Not sure why??? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 6, 2009 Report Share Posted January 6, 2009 No eth2: #This file was automatically generated by the IP PBX. auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 70.x.x.x network 70.x.x.x netmask 255.255.255.192 broadcast 70.x.x.x gateway 70.x.x.x auto eth1 iface eth1 inet static address 1.1.1.1 network 1.1.1.0 netmask 255.255.255.0 broadcast 1.1.1.255 Log File shows: Logfile Clear or Reload the log. [1] 2009/01/05 16:31:15: Starting up version 2.1.0.2115 [8] 2009/01/05 16:31:15: Route: eth0 462a4400 ffffffc0 [8] 2009/01/05 16:31:15: Route: eth1 01010100 ffffff00 [8] 2009/01/05 16:31:15: Default Route uses 70.x.x.x [7] 2009/01/05 16:31:15: Found time zones AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET CST CAT IST GMT [1] 2009/01/05 16:31:15: Working Directory is /pbx [5] 2009/01/05 16:31:17: Starting threads [7] 2009/01/05 16:31:17: UDP: Opening socket [0] 2009/01/05 16:31:17: UDP: bind() to port 5060 failed [0] 2009/01/05 16:31:17: FATAL: Could not open UDP port 5060 for SIP [7] 2009/01/05 16:31:17: Opening TCP socket on port 5060 [7] 2009/01/05 16:31:17: Opening TCP socket on port 5061 Not sure why??? Oh there is probably an old PBX running still (don't reboot the box until the problem is solved!). You can find the process with netstat (e.g. netstat -anp|grep 5060). Kill it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.