Jump to content

Bill H

  • Posts

  • Joined

  • Last visited

Contact Methods

  • AIM
  • ICQ

Profile Information

  • Gender
  • Location
    New Hampshire

Recent Profile Visitors

12,254 profile views

Bill H's Achievements


Newbie (1/14)



  1. I have a customer that wants to move his PBXNSIP Version 3 from one computer to a newer computer. He does not want to upgrade since his current Version 3 doeas all that he needs. Is there a link that can be made available for the older Windows 32 Installer for Version 3? Or is there an alternative method to do this. Thanks...
  2. I have seen this before, although it was some time ago. If I remember correctly, there is a Gain Control/Setting for Received DTMF or just a simple Gain Control in the Gradstream FXO Gateway. Try reducing the Inbound Level to a lower value.
  3. Thank you for your response. The scanner is not trying to Register at all, they are just sending a fake Invite to the CS-410. Why would this type of call ring the first extension in the CS-410? Also, the scanner is using a 46.4.100.xxx IP Address. Can I use with to block all packets from the entire range? Thanks again
  4. I have an older PBXNSIP CS-410 Version 3 system where someone, or more likely something (scanner), is trying to make calls to foreign countries. Since the customer does not make international calls I have blocked the International Calling Code of 011 and the telco service provider has also blocked it. That stopped that portion of the trouble. A SIP Trace shows that the calls were from an Unregistered Extension. What happens now is that these Unregistered Extension calls go to the first extension (Ext 221) in the CS-410 and end up in that persons mailbox as dead air. I did catch the IP Address of the scanner once and placed it in the Access Blocked Table, but it seems they change their IP Address to get around the blocking. I looked for a feature within the CS-410 to block Unregistered Extensions from making calls, but did not see anything that looked like it would do the job. My next and maybe last option is to block Access to everything except certain IP Addresses in the Access area. Does anyone have any additional ideas? Thanks.
  5. We have a remote extension that will initially register and then appears to not re-register. I looked at the registration area in the PBX and it shows the Dialogs Registered for the BLF buttons and the phone/extension too. Then after the registration times out the Dialogs for the buttons are still there (and will re-register) but the phone/extension drops out of registration. I have seen something similar to this before and have resolved it by placing the remote phone in the DMZ of its local LAN Router. This time I did that and it does not resolve the trouble. Also, why do the Dialogs for the buttons re-register but not the phone/extension? Thanks
  6. I went down the same path. I registered and I could not find any area on the site to get a license. Perhaps someone could show us the way...
  7. Thank you for your response. I will get a screen capture prepared. How about my second question.. SnomOne Blue states that up to 40 non-Snom phones can be used. Is this correct?
  8. I have asked these questions before, but I don't remember the answers. We have PBXnSIP Version 3 dot something and are considering moving up to the latest version of SnomOne. Can we re-use any portion of our existing XML Files when migrating? SnomOne Blue states that up to 40 non-Snom phones can be used. Is the correct? Thanks
  9. My associate has been calling for over a week, left messages and has not had any response from Snom/PBXNSIP. Can I get a good number to call????
  10. You need to Start a session first, From the CSTA Example page: Sent: <?xml version="1.0" encoding="UTF-8"><StartApplicationSession xmlns= =============================================================================================== Then if it is done correctly, you will receive something like this: Again,from the CSTA Example page: Received: '\x00\x00\x01\xc0l ve<?xml version="1.0" encoding="UTF-8"?> <StartApplicationSessionPosResponse xmlns="http://www.ecma-international.org/standards/ecma-354/appl_session" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <sessionID>99bjucmahlernqjl55xx</sessionID> That is where you get the Session ID from. Just use it in any further CSTA Messages sent to the PBX.
  11. I think you are on the right track here. We do have 15 people using "Click to Dial" all day long with about 50+ calls per user. This adds up to well over 700+ "Click to Dial" calls a day. You stated: "Maybe there error handling on the click to dial has some issues." Who would there (their) be? Is this something internal to PBXnSIP or caused externally?
  12. Thank you for your input(s). I have seen first-hand the "Fake Registration Flood" via Wireshark. Since we have Version 3 I usually stop the service, add the offending IP Address to the Access Folder manually and restart the service. A little awkward but it works. In this case, this is not the source of the trouble since Wireshark shows no flooding. I believe that we have not moved to Version 4 (SnomOne) is because the File System (XML) is different and we may need to re-program everything. Am I correct on this or not? Any other ideas???
  13. Übersetzt mit Google Translate Bitte entschuldigen Sie mein Deutsch. Version: (Win32) pbxnsip Ziemlich oft, wenn ich in Status aussehen / Anrufe sich Anrufe auftauchen, die 2 Stunden (oder mehr) mit alten "Alarmierung" sind Wenn ich überprüfen, um 04.00 Uhr das ist, was ich sehe: 2012.06.21 14.12.44 1408xxxxxxx @ localhost 256 @ localhost Alarmierung Auch in der pbx.xml Datei habe ich diese Datei: abgelaufenes-72561.txt Mit den folgenden Daten: Typ: Anrufer Von: <sip:1408xxxxxxx@localhost> To: <sip:256@localhost> Diversion: Extension: trunk: Start: 1340229259,37 Domain: 1 Call-ID: b7c0b4c9 @ TK-Anlage # 7155 IVR-Staat: c2d2 Wiederholung: Referenz: Staat: Alarmierung Und damit es noch interessanter, die Zahl 1408xxxxxxx @ localhost nicht aufrufen in. Unsere Erweiterung / User-256 @ localhost callte OUT ... Dies geschieht häufig während des Tages. Manchmal wird es das System sperren mit zu vielen "Alarmierung" nennt. Irgendwelche Ideen???
  14. Version: (Win32) PBXnSIP Quite often when I look in Status/Calls there are calls showing up that are 2 hours (or more) old with "alerting" If I check at 4PM this is what I see: 2012/06/21 14:12:44 1408xxxxxxx@localhost 256@localhost alerting Also, in the pbx.xml file I have this file: expired-72561.txt With the following data: Type: caller From: <sip:1408xxxxxxx@localhost> To: <sip:256@localhost> Diversion: Extension: Trunk: Start: 1340229259.37 Domain: 1 Call-ID: b7c0b4c9@pbx#7155 IVR-State: c2d2 Loop: Reference: State: alerting And to make it even more interesting, the number 1408xxxxxxx@localhost did not call in. Our extension/User 256@localhost made the call OUT... This happens frequently during the day. Sometimes it will lock the system up with too many "alerting" calls. Any ideas???
  15. Übersetzt mit Google Translate Version: (Win32) pbxnsip Wir haben dieses Problem seit einiger Zeit und es kommt und geht, ohne Sinn und Verstand, dass ich finden kann. Dieses Problem wurde in zwei verschiedenen Servern aufgetreten. Das Problem: Die Telefone nicht mehr funktionieren, weil die TK-Anlage wird mit 97% oder mehr der CPU. Normalerweise ist es rund 32%, wenn es ausgeführt wird. Ich halte an und starten Sie den Dienst pbxnsip und manchmal ist es beginnt zu laufen OK (mit 32% CPU-Auslastung) und manchmal muss ich anhalten und starten Sie es mehrmals (mit 97% CPU-Auslastung), bevor es normal läuft. That wird es wieder zu arbeiten bis zur nächsten Mal scheitert. Irgendwelche Ideen? Hat jemand dieses Problem gesehen? Ich habe eine zusätzliche Mühe, die ich glaube, ist unabhängig und wird es in separater Post zu schreiben.
  • Create New...