andrewgroup

Sorry for the slow reply - for the most part we try to stay agnostic on these boards in regards to brands.... But.... I'll admit we have a fair number of Linksys/Cisco SRW business series beginning with the 208P and up to and including STP stacks of the 224 and 248 series. All POE of course. However, many of these deployments were well before CISCO decided to whack the SRW series for competing with their other lines. The items are our immediate Radar are DLINK as a partner. Cheers.

1-Way Audio in almost all cases is the result of Firewalls, Routers, and Phone Firmware and or it's settings. PBXnSIP by nature would almost never have 1-way audio trouble otherwise. What can you easily eliminate? Firewall, routers, or Phones?

Would it be possible to create a counter that you reset daily (midnight) to indicate calls that dropped with 1 way audio? The email stuff is ok, but requires a parser or a set of eyeballs.... What is the latest list functions?

release 3194 seemed to introduce problems with the monitor extension buttons on snom 3xx phones. Rolled back to 3.2.0.3143 to stabilize the ext light troubles. (Will try 3198 later)

In realtime, I don't think so. But in the IPTRAFFIC using your tool of choice it's in the SDP packet. Have you re-orged the CODEC on the trunks. Knowing ulaw is 90K per call, can you grab the SNMP port stats for the PBX? That would give graphical evidence..

A far more workable and easier solution on smaller LANS is to simply use managed switches that support a MAC learning/locking on all ports and once deployed LOCK all ports to prevent the reference to someone adding a DHCP server. Since some users may wish to have access to the Phone interface, you would then have to create a route for the to subnets on the different VLANS. More Work... Since Many smaller installations will require a PC attached to a phone switch port, and not all phones will support VLANXXX for the Phone and VLANYYY for the PC Port. This gets complicated on layer2 switches and heaven forbid someone sticks a dumb switch in an office to get two usable ports as this will kill all your hard work. Your easiest and very reliable is as described above, and don't forget to learn and use all of the DSCP/QOS capabilities to ensure call quality.

Giving this some thought, "Brain Hurting ", I doubt a reasonable and workable solution exists within the confines of the web interface.

It all depends on latency. (IPSEC) has a 20% overhead... IF LOCAL LAN is 192.168.20.x and the PSTN GATEWAY is on a FOREIGN LAN 192.168.30.x using say .254 You would simply make the SIP trunk to the foreign IP 192.168.30.254 and let the routing table on the local firewall with the VPN link route the 192.168.30.x traffic to the next hop on the VPN link.... If you can keep the latency low and have adequate bandwidth this will work fine.

This will prove to be a management nightmare, as you'll still be forced to provide a AA or DID for each accountant as you'll never be able to predict where the source caller will place that call from and whoever said CID was dependable. Lots of busy work managing that.... Cheers.

We've found V3.2.0.3143 coupled with Snom Version 7.3.14 handsets to be stable. The newer cs410 firmware seems to have troubles keeping the buttons accurate where the button lites monitor co's and ext's The Snom 320's were somewhat more stable that the 360's but moving back to these releases resolved these intermittent troubles. FYI...

Sorry for the late Update, but the replacement CS410 has not failed in the last 14 days. Perhaps our original analysis of TSTP packets causing troubles wasn't totally the issue, but removing RSTP did extend the restart issues by 4 days, but the restarts continued but the new CS410 has been stable for 15 days... FYI... This was as new in the BOX cs410 that failed..... So the old adage, if things are going to fail, they will in the first 30 days...

The results are the random restarts continue. We'll open a paid support call for guidance and plan to fully replace the hardware with a new unit too.

5 days after the changes we get a restart. (Better than once a day, but still no client can tolerate that.) We see RIP V1 on the local LAN side of the ISP router and that's now turned off and we'll evaluate the results. what would be helpful, would be a small a 5 minute CRON job to gather some stats about the interface, memory, and cpu, that might provide a clue by writing to a series of files to a file to give us an indication of what might be causing a memory leak. Any word on the new Kernel or another update on the PBX or MSP file? (We don't think any of the SNMP values help much.) any thoughts?

FYI, so far our suspicions are correct and we see no random restarts now that the CS410 is not exposed to STP packets. What we are seeing from many vendors is that STP is enabled by default so as to protect against loops. So we advise to be certain to disable STP on all switch ports if possible or take you chances with a dump switch. (A router with SIP/port control is recommended if you have no access to the LAN switch) Cheers - AndrewGroup

To confirm these findings, configure a layer switch for STP and plug it into you lan and have it generate these stp packets. We saw this behavior on a Linksys SRW208P, and now a CISCO express 500. In the rarest of cases, we may have to put a router on the local lan to segment this traffic if our hunch is correct.

With a reasonable amount of certainty we believe the CS410 will consistently crash when it sees 802.1D spanning tree packets. The CS410 creates the following within TCPDUMP when it sees STP bridge packets from a CISCO express 500 switch. 15:54:33.774469 802.1d unknown version 15:54:35.787483 802.1d unknown version 15:54:37.801500 802.1d unknown version 15:54:39.372508 00:0d:02:83:7f:18 > 09:00:07:ff:ff:ff snap I (s=0,r=3,P) len=42 15:54:39.766503 00:14:f1:8f:68:01 > 01:00:0c:cc:cc:cc snap I (s=0,r=6,C) len=331 15:54:39.814516 802.1d unknown version 15:54:40.111524 IP 192.168.1.105.2082 > 192.168.1.99.sip-tls: P 22380:22932(552) ack 21013 win 14992 <nop,nop,timestamp 102751459 158489> 15:54:40.128011 IP 192.168.1.99.sip-tls > 192.168.1.105.2082: P 21013:21365(352) ack 22932 win 8406 <nop,nop,timestamp 159228 102751459> 15:54:40.129561 IP 192.168.1.105.2082 > 192.168.1.99.sip-tls: . ack 21365 win 14992 We had previously had a CS410 rebooting, and STP was disabled along with several other QOS improvements and that CS410 suddenly stabilized. A new installation is restarting daily without notice. We have a full 78MB Wireshark Trace for dissection. However, we cannot leave this configuration running for further testing, We will now disable STP on this switch and we fully expect to see the restarts stop... The Cisco Switch also shows about 200 error packets on the port with the CS410, And the switch logs a variety of malformed packets on the CS410 port The Switch in FULL auto has negotiated 100MB Half Duplex....

In the WIKI / Support site on the CS410 appliance a screen shows the frequency / cadences, is that screen still accessible?

The above is in place.. we are awaiting detail from the cable company on all issues for the settings in the ARRIS 504G media gateway. Hopefully we can delay until we get this information... How do we get to the advanced PSTN interface settings?

The Cable Carrier in question has agreed to get me the answers to our questions regarding how the default settings of the FXS media gateway is provisioned from the switch. What are the specific questions to ask, so that we can program the CS410 for best performance? IE Disconnect Wink Timing? We'll Post what we learn for all to know.. Cheers

We are seeing these from a recently installed CS410 The call between sip:123-456-0000@localhost;user=phone and sip:anonymous@localhost;user=phone has been disconnected because of media timeout (120 seconds), 0/5931 packets have been received/sent We are seeing these on all three analog ports... My guess is the call is ended, but the PBX is not detected the hangup and timing out... Investigating this, the first attempt to reach the WEB interface failed, and in a moment or two we recieved the "System start" email from the PBX we just tried to reach. It's as if the HTTP stream forced the reset and this isn't the first time these two events seemed related.. Running 3.4.0.3194 (Linux) MSP 828_v2_03_01 Release 2.4.2 The FXS interface is a Arris Touchstone TM504G/NA cable DOCSIS 4 port FXS media Gateway And the installation tech had no details on CPC timing,,, This device is commonly used by Comcast and other Cable providers when selling dial-tone.. Does anyone have the details on the CPC settings for this device? Cheers,

Jumped right off of that build for the IP address change issues. Installed 3 CS410's in last two weeks on the following build. We have shared lines on Snom phones all working as expected. Version: 3.4.0.3194 (Linux) License Status: pbxnsip CS410 License Duration: Permanent Additional license information: Extensions: 3/10 Accounts: 17/20 Working Directory: /pbx MAC Addresses: 0019156BF918 0019156BF919 Calls: 326/4 (CDR: 399) 0/0 Calls SIP packet statistics: Tx: 56132 Rx: 56358 Emails: Successful sent: 71 Unsuccessful attempts: 1 Available file system space: 69% Uptime: 2009/6/19 17:28:44 (uptime: 8 days 00:21:57) (6010 6513088-0) WAV cache: 1

We've experienced slowness and other strange issues when using IE8.. Ran accross this tip in another forum.. <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"> will force IE8 to use the IE7 rendering engine.. FYI...

OK, maybe this is my fault, I've re-read http://wiki.pbxnsip.com/index.php/Service_Flag I'm switching to Military time on all SF. I think you cannot have 12hr times on Mon and Military times on Tues.... Have you noticed that IE8, seems to time out or require refreshes, I've set the refresh pages on all visits, I sometimes deleted temp files too...

It's taken nearly 4 hours of develop, and countless business interuptions for a client what would have taken 10 minutes if only we had a button to FORCE the PBX to read the status of the service flags. Waiting and hoping has been a royal pain.

Indeed that does work, but I feel like the car salesman taking each deal to the manager for approval. An official policy or process will go a long way. Cheers,