andrewgroup

When accessing the dial by name directory, and the caller enter 2 or 3 digits depending on the search settings, if it finds a unique match, it immediately transfers the caller to the matching extension. However, many people don't know the correct spellings, and it would be preferred the system would play a message. To reach "NAME recording" press 1, otherwise press any key to return to the directory. Individual accounts should have a Directory Opt Out setting too..

The Guru plug shows only 512MB Ram, isn't that the amount in the old White CS410's that was upgraded to 1GB in the Black units? Our hopes would be to provide Marvell ARMADA™ 168 800MHz , 512MB DDR2-800

The last time I applied an update file, I think it was the .1025 release, it overwrote the entire configuration.... What is the recommended way to apply the binary upgrade? Will the latest release run properly with the configuration files of these releases 4.2.0.3966, 4.2.0.3981

What vendor and model # are you using as the test environment?

We may soon decide to replace a number of CS410 appliances with Sheeva Plug computers. I am interested to know the experiences people are having, and what appliance they are running on. There seems to be some confusioin in the marketplace regarding the plug hardware platform. http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit-us.aspx I would also hope that Snom has adopted a specific platform for testing purposes. We have a very experienced Linux veteran ready to to assist us in creating a default package, but want to get off on the correct footing..... All thoughts appreciate..

IF this is the case, what can we do to help determine the cause and obtain a potential fix? Do you know of a way to force a REBOOT on CS410's Weekly, until such a solution or option can be addressed? On a personal note, I'm willing to scrap all CS410's now in the field in clients at my expense and replace them with Sheeva plugs if that results in a more stable environment to run the PBX Software.

for all practical purposes it appeared to me the registration was a success. But the phones and PBX showed otherwise. Immediately after a restart, I duplicated the capture progress form the same phone that had not been restarted of changed. It may take a few weeks for this to occur again, and considering this particular client, I won't have much time to play around, but if you think a specific piece of information may help isolate the issue, give me the scripts, commands to execute and I'll be glad to do that... We have two clients that are experiencing the issue. One phone remained registered out of 6, but I did not reboot it to see if it would re-register.... (perhaps some weird snom phone setting is to blame, that's on all other phones...

YES, I think the TCPDUMP command was' tcpdump -i eth2 -s -o host 192.168.1.101 -vvv -w \home\failed

Really, We've seen this occur recently on both 4.2.0.3966 and the attached files are from release 4.2.0.3981 taken yesterday. The attached files are TCPDUMP captures from the PBX watching a specific HOST (Phone that doesn't register) The file named failed was taken before the PBX restart and captures the attempt by the phone to re-register... The file named good is the same capture, after the PBX was restarted. No other changes were made on the network, the phone was not restarted, The captures look surprisingly similar, but one fails to register, the other is a success. cpas-failed.zip

On the two release versions immediately prior to release 4.2.1.4025 we've experienced at least 4 occasions where phones will not properly register until the PBX is rebooted. I've read the release notes on the newer versions including the 4.3 release, but I see no mention of a bug fix related to phones being registered. We are happy to upgrade to the latest, but would like to know if the condition I speak of has been seen and addressed in ..4025 or the 4.3 release? To help, just prior to a reboot, we've captured a TCPDUMP file from a specific phone IP address and attempted a re-register after the PBX reboot, we captured the same successful file... reviewing these in Wireshark, they look amazingly similar, but someone with a lot more experience may be able to determine the issue, and perhaps this might indicate a potential bug... On one PBX the failure occurred after about 45 days of uptime..... and 700 calls.... Lots of available space plus no logging going on... Any advice is appreciated.... A scheduled reboot once per week would be helpful, but I understand CRON is not in the PBX OS.... any suggestions for a weekly scheduled reboot?

I have no idea how to add attachments to this board. I've sent the trunk pcap file to KM and MD requested emergency help..

I will post or PM a pcap file from the trunk

Windsream Formally Nuvox, has made a change on theor Sonus platform and three clients using windstream now fails, Windstream support in working late into the night to determine what has changed on their end. After the invite, PBX provide 100 trying, then a progress 183, followed by a 400 Bad Request. Absolutely nothing had changed on all three clients, each with dedicated SIP services and all three failed at same time... I hope to here something yet tonight or in the AM, hoping to get a heads up if possible.. The call looks like this skipping the details. I think an update on the Sonus warrants a trunk settings change.... Any advise helpful. |Time | 74.223.147.173 | | | | 173.221.11.118 | |0.000 | INVITE SDP (g711U g711A g723 g729 g721 telepho...eventRTPType) |SIP From: "GREENVILLE SC" <sip:8649184278@74.223.147.173:5060 To:<sip:6566736005@171.222.11.118:5060 | |(5060) ------------------> (5060) | |0.013 | 100 Trying| |SIP Status | |(5060) <------------------ (5060) | |0.083 | 183 Session Progress SDP (g711U telephone-even...PType-101) |SIP Status | |(5060) <------------------ (5060) | |0.143 | 400 Bad Request |SIP Status | |(5060) <------------------ (5060) | |0.200 | ACK | |SIP Request | |(5060) ------------------> (5060) |

We have this version 4.2.0.3981 on a client and when entering the cell phone number in the redirect field it accepts it as entered. On another running 4.2.1.4025 when you enter the cell phone number for the extension it rewrites the cell phone and adds "-" dashes between making the entry 617-222-3333 On the 4025 machine the offer virtual assistant does not work, while the 3981 does.... Is there a setting to prevent the "-" from being added? read all pages from book regarding cell phone and no love. Please advise.

When did the WAN / LAN ports become reversed whereas the WAN port is static IP to 192.168.1.99 by default and the LAN is DHCP? What is needed on the latest release to support Audio In on the rear of the cs410? What is needed to support the PAGE out on the CS410?

We downloaded 4.2.1.4025 upgrade and installed the executable into a running windows pbxnsip version 4.2.1.4002 The upgrade license is OK through the September. The PBX service starts just fine but no calls, immediately restoring the original EXE file, all returns to normal. We weren't able to and had no time to do much diagnosis, but previous updates worked as expected. Might there be some subtle changes that might result in the problem, and you can save us a lot of investigative work? Thanks -

The link was unable to open a CS410 version. Will this be a Full package, or simply a binary upgrade?

Our first two appliances, Pure Sip trunk service on the first and 8 analog lines on the second, went extremely smooth, and in each case we deployed these units and had them up and running prior to reading the manual. I do not recall that disabling the DHCP server was difficult. We did have an issue with the Sangoma Card on the second unit, but we posted tips to help others. both units are fully PNP with Snom 300, 320, and M9 handsets. Building a WINDOWS or LINUX vs THE SNOM ONE APPLIANCE. We are in the Sales Support business and the later is an extremely cost affective solution and looks and operates professionally, and takes less than 1 Hour to deploy.

The system is present set no to compress recordings. We were given a short term license just outside the 1 year support plan for this client to address another issue. The expiration to upgrade to the latest appears to have passed. the client has expressed hesitation to invest in an upgrade to SnomOne Blue, with this outstanding issue. What should we do? Version: 4.2.1.4002 (Win32) Created on: Mar 10 2011 17:16:27 License Status:Client Name Pro 50 rekey 00902713XXXX License Duration: Permanent Additional license information: Extensions: 46/50 Accounts: 101/150 Upgrade: 6 28 2011

We have a client running PBXnSIP 4.2.1.4002 (Win32) And the problem is a busy extension, 163 (accounts receivables from customers) receives a lot of calls. Circumstantially, and randomly the 3rd voice mail left on a given day has an unusual set of fast tones, beeps. When hearing the message, you hear the person grumbling, then some tones and a hangup. My thoughts are, perhaps a cell carrier or central office switch isn’t “tearing down” the call normally, CPC stuff, and Windstream the SIP carrier, creates these unusual tones. With this happening on just one extension, the one that normally gets upset callers, it might be related to the carrier. We have a tech call to the carrier, and the next step is we will passively record the entire SIP trunk calls, and get a complete Wireshark trace too. I think we need to Isolate the following PHONE - SWAP Phone with Other Extension PHONE - LAN - PBX CONNECTION (Move Phone to other port/switch) PHONE - FIRMWARE UPGRADES Any comments appreciated - Andy

check the obvious stuff. Has security clobbered the ip addresses ranges Call me crazy, but our crafted Centos and Windows PBX's have public facing IP addresses, Are your trunk provider interfaces separate nics? Are they static Routed to the Carrier? Can you duplicate this with a NON-SNOM, soft - Phone Etc. While PBX traces are Ok, a passive wireshark trace tells a much more complete story. The Goal in any troubleshooting scenario is to ask questions and take small incremental steps so that the only answer to the question being asked is YES or No. Hopefully you can take a SWAG at the first question so isolate the system into two parts. then take action and when looking at the evidence you can determine is this a problem 100% on the left or right side of where you are looking. Is the problem on the trunk or caller side? Does the same issue exist with another NIC? and on, and on, and on, Good Luck. Andy

Can we see a CS410 compile of SnomOne Free?

If or when will SnomOne tightly integrate with Snom Phones. By this I mean control the many settings in the phones from a WEB interface on the PBX. We are fine with PNP, and buttons, but being able to set global Snom Settings in the PBX and control on a EXT by EXT basis the many other settings that you commonly will need to adjust. Might this be on the Road Map?

OK, I have an admission in that I simply don't read as much as needed prior to new products and doing so, wasting some time. Some years ago a product came with a sheet that said "If you don't read manuals and quick start guides at leasr read this!" Based on this FXO installation I would begin with the following tips. 1. Assume this system is not 100% configured from the box. 2. (If you do not successfully configure the Sangoma FXO board, the GATEWAY will not start) HINT, HINT, HINT See hint 4 3. Don't use Internet Explorer 8.0, (The Sangoma config web pages don't display) 4. You must perform the Sangoma Configuration "Quick Wizard" Note Expand your web browser, the Next button is in the far lower right Corner. 5. Always performline calibration tests. (this improves the echo cancellation and CPC signal handling) I also think an adendum about the Sangoma card and all associated utilities would be a big plus with each unit. Things I don't like. If you choose to wall mount the Chassis with the enclosed brackets, you are forced to removed it from the wall if you wish to remove the cover. (It would be nice if the chassis stayed.) I hope this helps someone

We have recently had a "clean build of CENTOS" created for a specific appliance and was curious how the PBX installation is supposed to correctly tag the packets with the default DSCP packets? Does this require and specific package allowing specified packages to tag packets? Can you provide details. Thanks