mabbott
Members-
Posts
43 -
Joined
-
Last visited
mabbott's Achievements
Newbie (1/14)
0
Reputation
-
Can I get a link to where I can get a pbxnsip build of 4.2.0.3966, I tried the other day to used the link on the website, changing the build number to 3966, downloaded the file, but it has the executable for build for 4.2.0.3981. Thanks.
-
I was just playing with this yesterday. You just need to add 127.0.0.1 mask:255.255.255.255 to the Allow list.
-
Version:3.4.0.3201 The MWI/message count seems to not be getting updated when a moving a message is completed in a call to a mailbox. I am not seeing any notifies being sent from the system to update the message counts. I have done a few tests using an auto-provisioned Snom 370 as the only phone on an extension. Test 1: 1new/0saved indicated on phone and pbx, log into mailbox using phone and move message to another extension, message appears on other extension, however pbx says 0/0 but phone still says 1/0. Test 2: 2new/0saved indicated on phone and pbx, log into mailbox using phone and delete one message then move 2nd message to another extension, message appears on other extension, however pbx says 0/0 but phone still says 2/0. If deleting or saving all messages or using the * code to clear the MWI, the message counts will be updated/cleared on the phone.
-
I thought this worked for other feature codes beyond DND? I changed enable/disable forward all to the same code and it always says forwarding is disabled.
-
Yes, you are right, it is just a Javascript error. I changed it in the config file and it does toggle the features.
-
From Wiki "If the codes for DND on and off are the same, the PBX toggles between the two states. This is useful if you have a phone that just has DND programmed as a speed dial button." Has this feature been removed in 3.4? I cannot enter the same * code in DND on and off. This is useful for other codes beyond DND as well.
-
hmm, I just noticed something. If I restart pbxnsip once the computer is up an running, it will then work correctly, but if i reboot the computer, it doesn't come up correctly. Is pbxnsip maybe starting before the networking is totally up? Here are 2 logs, 1st is after a reboot 2nd after restarting pbxnsip. 1]Â 2009/09/25Â 09:28:37: Starting up version 3.4.0.3201 [7]Â 2009/09/25Â 09:28:37: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 GMT+3 GMT+4 GMT+5 GMT+6 GMT+7 GMT+8 GMT+9 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 GMT [8]Â 2009/09/25Â 09:28:38: Scheduler precision is 0 us [1]Â 2009/09/25Â 09:28:38: Working Directory is /Library/pbxnsip [5]Â 2009/09/25Â 09:28:38: Starting threads [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on 0.0.0.0 [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on [::] [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on 0.0.0.0:5060 [8]Â 2009/09/25Â 09:28:38: Joined multicast group 224.0.1.75 [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on [::]:5060 [1]Â 2009/09/25Â 09:28:38: UDP: TOS could not be set [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on 0.0.0.0:5060 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on [::]:5060 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on 0.0.0.0:5061 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on [::]:5061 [5]Â 2009/09/25Â 09:28:38: Set scheduling priority to 15 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on 0.0.0.0:80 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on [::]:80 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on 0.0.0.0:443 [7]Â 2009/09/25Â 09:28:38: TCP: Opening socket on [::]:443 [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on 0.0.0.0:161 [7]Â 2009/09/25Â 09:28:38: UDP: Opening socket on [::]:161 [0]Â 2009/09/25Â 09:28:38: Could not open UDP port 69 for TFTP [0]Â 2009/09/25Â 09:29:17: Last message repeated 2 times [3]Â 2009/09/25Â 09:29:17: SMTP: Cannot resolve smtp 1]Â 2009/09/25Â 09:34:05: Starting up version 3.4.0.3201 [7]Â 2009/09/25Â 09:34:05: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 GMT+3 GMT+4 GMT+5 GMT+6 GMT+7 GMT+8 GMT+9 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 GMT [8]Â 2009/09/25Â 09:34:05: Scheduler precision is 0 us [1]Â 2009/09/25Â 09:34:05: Working Directory is /Library/pbxnsip [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on 192.168.1.139 [5]Â 2009/09/25Â 09:34:05: Starting threads [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on 0.0.0.0 [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on [::] [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on 0.0.0.0:5060 [8]Â 2009/09/25Â 09:34:05: Joined multicast group 224.0.1.75 [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on [::]:5060 [1]Â 2009/09/25Â 09:34:05: UDP: TOS could not be set [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on 0.0.0.0:5060 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on [::]:5060 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on 0.0.0.0:5061 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on [::]:5061 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on 0.0.0.0:80 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on [::]:80 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on 0.0.0.0:443 [7]Â 2009/09/25Â 09:34:05: TCP: Opening socket on [::]:443 [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on 0.0.0.0:161 [7]Â 2009/09/25Â 09:34:05: UDP: Opening socket on [::]:161 [0]Â 2009/09/25Â 09:34:05: Could not open UDP port 69 for TFTP
-
Yes, it does have the name server that I want to use. I have also tried multiple name servers with the same results.
-
I am having an issue with my install on OSX resolving dns entries(pbx version 3.4.0.3201). I believe it started when I upgraded to Snow Leopard (10.6), but I am not 100% sure. The logs are showing errors trying to resolve both my email server and trunk registration server. If I change either to the servers ip, the email gets sent or registers the trunk. The computers DNS servers are correct and will resolve both hosts properly.
-
This is an option on the Snom phones. There is a setting called "Dial tone during hold" under advanced-->audio that is used to disable the dial tone or set cw_dialtone to off in one of the snom_xxx_custom.xml config files to change it globally.
-
The 3.4 build did not solve the problem. It still isn't switching back to inband dtmf when 2833 is removed from the re-invite.
-
Can I get this in a 3.3 cs410 version to test? The carrier won't give me a number to test the beta with and I can't test this with the customers equipment.
-
I would need a build for a CS410.
-
Is there a setting for force to inband? Or would this require a new build for a fix?
-