Jump to content

CS410 dies after 30 seconds or so?


Bradley_M
 Share

Recommended Posts

We just recently received a black CS410 (P/N - 261-451280R) and it was working until this morning. I tried to get to the unit via static IP address, and no go. The phones aren't registering to it . . . I turned it off, then got it back up for a brief time . . . just long enough to change the static IP address to dynamic. I fired it back up and I can see it in our DHCP table on the router, so I go to it's new dynamic IP address. I can use it for a certain length of time . . . maybe 30 seconds to a minute after it is up on the network and then it dies. I've unplugged it and let it sit for 15 minutes, then plugged it back in . . same thing. I tried telnet to the unit and was looking around and in the midst of that it will just stop communication and drop. I still have power/run/lan lights on the front. I've hit the reset button on the back (are there any instructions on how to use that?) and no luck there either. You can imagine my frustration level . . . I've just been dealing with getting my Snom360 display issues sorted out (a fix for the ribbon connector failure problem will posted soon).

 

I called the phone number on the web site and experienced horrible stutter issues while trying to talk to a tech . . . who said to go here . . . or wait for a call back. I'm *still* waiting.

 

Any suggestions?

 

Many thanks!

Link to comment
Share on other sites

We just recently received a black CS410 (P/N - 261-451280R) and it was working until this morning. I tried to get to the unit via static IP address, and no go. The phones aren't registering to it . . . I turned it off, then got it back up for a brief time . . . just long enough to change the static IP address to dynamic. I fired it back up and I can see it in our DHCP table on the router, so I go to it's new dynamic IP address. I can use it for a certain length of time . . . maybe 30 seconds to a minute after it is up on the network and then it dies. I've unplugged it and let it sit for 15 minutes, then plugged it back in . . same thing. I tried telnet to the unit and was looking around and in the midst of that it will just stop communication and drop. I still have power/run/lan lights on the front. I've hit the reset button on the back (are there any instructions on how to use that?) and no luck there either. You can imagine my frustration level . . . I've just been dealing with getting my Snom360 display issues sorted out (a fix for the ribbon connector failure problem will posted soon).

 

I called the phone number on the web site and experienced horrible stutter issues while trying to talk to a tech . . . who said to go here . . . or wait for a call back. I'm *still* waiting.

 

Any suggestions?

 

Many thanks!

 

 

Hi,

 

dynamic IP ...havn't tried that, might try to set it back to fixed ip, and look at your router, makes sure your fixed ip is not with in the range of DHCP address on the router,,,mine does not like the two mixed, when it is I cannot get to anything that is assigned an IP address that should be assigned by DHCP, I just have an old network anywhere NR041, it seems to handle my 3 Snom 300 phones ok and 2 PSTN phone lines, it does have its share of issues though, I am finding out VOIP is not for the faint of heart, I am fixing to try a Sip Trunk pretty soon, have gotten a lot of bugs out of the PSTN thing though, make sure also that the phones if using fixed ip are not in the range of DHCP also...

 

you did not mention much about your configuration...be nice to know what phones you are using how many, how many pstn lines, do you have a sip trunk, what kind of router etc....

 

Also the phones like to have a fixed ip's also, at least mine do, it works better than using the mac address, maybe it has someting to do with the router, dont know..I am just a user like you on the forum..

 

I am familiar with the 300 Snom phones, my router, and this device, only...and Bogen Quantum VOIP

 

Best Regards, ;)

Link to comment
Share on other sites

Also you might want to make sure you are running the lastest software, check for version under Status

 

http://www.pbxnsip.com/software

 

"You should also update the DSP code since we make some changes. We updated the wiki page yesterday check out section two. cs410 wiki page"

 

http://wiki.pbxnsip.com/index.php/Installi...P-PBX_Appliance

 

and a good SSH for crawling around in it...

 

http://winscp.net/eng/download.php

 

;)

Link to comment
Share on other sites

you did not mention much about your configuration...be nice to know what phones you are using how many, how many pstn lines, do you have a sip trunk, what kind of router etc....

 

Ok, so far I have 6 SNOM 360 phones (Here's my screen fix for the screen issues - http://www.instructables.com/id/SNOM-360-Display-Fix/) and just a single POTS line for my PSTN side right now at my test lab. I will be deploying this at a location with with 4 SNOM 360's and one courtesy phone that is a SNOM 320 with 4 POTS lines. I have my SNOM's flashed to 6.5.15 and 5.5.1 (I don't know what's up with some of them not flashing beyond that yet, but that doesn't affect this issue). I have a CISCO 10/100 16-port VPN Router on Firmware Version: 2.0.3. When I turn the CS410 on I see in the DHCP table that it gets an IP address . . . and I can ping it. I can then also telnet to the box. In the middle of navigating the directory structure the unit will die . . . I haven't timed it exactly but I'd say I get about 1 minute into it and then it just stops responding. Sometimes after resetting, I can get the HTTP based screens up, but many times they fail too. I've tried the reset button on the back, but I suspect that just interrupts power to the unit?

Link to comment
Share on other sites

In fact . . . I just did a test . . . I turned on the unit and started pinging the IP address that the DHCP client was handing off at the same time. You can see exactly how long the unit comes online and then subsequently fails. Here's the interesting details:

 

C:\Documents and Settings\Bradley Miller>ping 192.168.1.113 -n 1000

 

Pinging 192.168.1.113 with 32 bytes of data:

 

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 192.168.1.113: bytes=32 time=6ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Reply from 192.168.1.113: bytes=32 time<1ms TTL=64

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 192.168.1.113:

Packets: Sent = 19, Received = 8, Lost = 11 (57% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 6ms, Average = 0ms

Link to comment
Share on other sites

In fact . . . I just did a test . . . I turned on the unit and started pinging the IP address that the DHCP client was handing off at the same time. You can see exactly how long the unit comes online and then subsequently fails. Here's the interesting details:

 

Hmm. That more looks like a problem with the startup - maybe file system full or something going wrong with the firmware update? Maybe a problem with the watchdog timer? In any case, it is worth to try to SSH in and use the few seconds alive to kill the last bash process. That should hopefully stop the madness and give you time to look around what the problem is.

Link to comment
Share on other sites

Hmm. That more looks like a problem with the startup - maybe file system full or something going wrong with the firmware update? Maybe a problem with the watchdog timer? In any case, it is worth to try to SSH in and use the few seconds alive to kill the last bash process. That should hopefully stop the madness and give you time to look around what the problem is.

 

 

Any hints on what to kill????

 

comcerto:~# ps aux|more

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

root 1 13.0 0.4 1512 492 ? S 2007 0:10 init [2]

root 2 0.0 0.0 0 0 ? SN 2007 0:00 [ksoftirqd/0]

root 3 0.0 0.0 0 0 ? S< 2007 0:00 [events/0]

root 4 0.0 0.0 0 0 ? S< 2007 0:00 [khelper]

root 5 0.0 0.0 0 0 ? S< 2007 0:00 [kthread]

root 6 0.0 0.0 0 0 ? S< 2007 0:00 [kblockd/0]

root 7 0.0 0.0 0 0 ? S 2007 0:00 [pdflush]

root 8 0.0 0.0 0 0 ? S 2007 0:00 [pdflush]

root 10 0.0 0.0 0 0 ? S< 2007 0:00 [aio/0]

root 9 0.0 0.0 0 0 ? S 2007 0:00 [kswapd0]

root 11 0.0 0.0 0 0 ? S 2007 0:00 [mtdblockd]

root 185 0.0 0.9 2220 1044 ? Ss 2007 0:00 dhclient3 -pf /va

r/run/dhclient.eth0.pid -lf /var/run/dhclient.eth0.leases eth0

daemon 202 0.0 0.3 1632 440 ? Ss 2007 0:00 /sbin/portmap

root 230 0.1 0.6 1724 664 ? Ss 2007 0:00 /sbin/syslogd

root 233 0.0 0.3 1512 440 ? Ss 2007 0:00 /sbin/klogd

root 241 0.0 0.4 1572 508 ? Ss 2007 0:00 /usr/sbin/inetd

root 268 0.9 0.4 5140 444 ? S 00:00 0:00 /pbx/sipfxo --con

fig /etc/sipfxo.conf --agc --busy-det --show-version /etc/sipfxo-release --pbx-a

dr 127.0.0.1 --sip-adr 127.0.0.1 --csp-mac 00:19:15:68:40:A0 --msp-mac 00:1A:1B:

1C:1D:1E

root 269 0.0 1.1 2684 1236 ? S 00:00 0:00 /bin/bash /etc/rc

2.d/S20pbxnsip start

root 270 50.3 21.5 41644 23812 ? S 00:00 0:22 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 275 0.0 0.4 5140 444 ? S 00:00 0:00 /pbx/sipfxo --con

fig /etc/sipfxo.conf --agc --busy-det --show-version /etc/sipfxo-release --pbx-a

dr 127.0.0.1 --sip-adr 127.0.0.1 --csp-mac 00:19:15:68:40:A0 --msp-mac 00:1A:1B:

1C:1D:1E

root 276 0.0 0.4 5140 444 ? S 00:00 0:00 /pbx/sipfxo --con

fig /etc/sipfxo.conf --agc --busy-det --show-version /etc/sipfxo-release --pbx-a

dr 127.0.0.1 --sip-adr 127.0.0.1 --csp-mac 00:19:15:68:40:A0 --msp-mac 00:1A:1B:

1C:1D:1E

root 277 0.0 0.4 5140 444 ? S 00:00 0:00 /pbx/sipfxo --con

fig /etc/sipfxo.conf --agc --busy-det --show-version /etc/sipfxo-release --pbx-a

dr 127.0.0.1 --sip-adr 127.0.0.1 --csp-mac 00:19:15:68:40:A0 --msp-mac 00:1A:1B:

1C:1D:1E

root 279 0.0 1.3 4040 1508 ? Ss 00:00 0:00 /usr/sbin/sshd

root 285 0.0 0.7 1864 780 ? Ss 00:00 0:00 /sbin/rpc.statd

root 291 0.0 0.4 1508 480 ttyS0 Ss+ 00:00 0:00 /sbin/getty -L tt

yS0 115200 vt100

root 299 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 300 0.2 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 301 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 302 0.1 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 303 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 304 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 305 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 306 0.0 21.5 41644 23812 ? S 00:00 0:00 /pbx/pbxctrl-debi

an3.1 --dir /pbx --default default.xml --no-daemon

root 307 1.7 1.9 7024 2180 ? Ss 00:00 0:00 sshd: root@pts/0

root 309 0.0 1.9 7024 2180 ? S 00:00 0:00 sshd: root@pts/0

root 311 1.0 1.3 2744 1448 pts/0 Ss 00:00 0:00 -bash

root 315 0.0 0.7 2664 864 pts/0 R+ 00:00 0:00 ps aux

root 316 0.0 0.5 1872 632 pts/0 S+ 00:00 0:00 more

comcerto:~#

Link to comment
Share on other sites

Is there a update.tgz in the /pbx directory? If yes, delete it. Maybe also rename the /etc/init.d/pbxnsip to something else.

 

I *think* I found the smoking gun here . . . is that WAN port still accessible despite no connection? I yanked the system and put it on my test network and it started working . . . moved it back and it died again . . . finally looked and decided to yank the WAN off fixed IP and put it on DHCP too temporarily . . . . viola . . . problem seems to be fixed. I suspect that when my users came in on Monday, .99 got handed out on DHCP request, causing issues . . . but I'm curious as to why the unhooked WAN would have had any influence here???? Hmm. My VAR still hasn't replied to my earlier message, and as of yet, the replacement device isn't here yet either. This could coincide with the documentation issues mentioned by other resellers in the forums that I've read about . . . hmm.

Link to comment
Share on other sites

  • 3 weeks later...
Whow you mean it could be that the WAN is still on DHCP while the startup script is already running and the watchdog timer kicks in?

 

 

hi, i also experience the same issue. when connect to LAN port with DHCP the LAN connection will die off after sometimes. The LAN LED indicated also off. i have not issue on WAN Port with fixed default ip 192.168.1.99. below is my CS410 box info.

 

Version: 3.0.0.2898 (Linux)

License Status: Appliance Key

License Duration: Permanent

Additional license information: Extensions: 10/32 Accounts: 16/40

Working Directory: /pbx

IP Addresses: eth2 192.168.1.99 192.168.1.0 255.255.255.0

eth1 1.1.1.1 1.1.1.0 255.255.255.0

lo 127.0.0.1 127.0.0.0 255.0.0.0

default 192.168.1.99

MAC Addresses: 001915683F61 001915683F60

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...