voipguy

Hi pbx support, The dial plan is the same - all we did was upgrade from ver 4.0.1.3438 to 4.0.1.3442 that's it - we never changed anything else and now the *67 doesn't work.

Hi Maslym, Thanks for testing it. Pbxnsip - any suggestions on why it's not working for my system? We are useing centos 5 64 bit with PBXNSIP ver 4.0.1.3442.

It doesn't work. Doesn't matter which computer I use or web browser, the end user can't change their web password. This is how I tested: 1. Opened up web browser and went to domain that customer is in. 2. Entered customer login name - 4166381234@test1.mydomain.com 3. Entered password. 4. Login Type is Automatic 5. Went to settings, changed web password to test1234 did the repeat password. 6. Clicked Save 7. I logged out. 8. Closed web browser - opened new web browser. 9. Tried logging in with new password and it doesn't work - I can use the old password and that lets me login. 10. Tried this from different computers/web browsers and still doesn't work. Is your test system setup as a multi domain? If yours is not could that make a difference as to why yours works and mine doesn't? I know it made a difference with one other bug report where your tech said it works for them but not me until I said make sure your testing in a multi domain system and not just localhost...soon as he changed it to multi domain he was able to duplicate the bug on his end. If you are testing on a multi domain system and it works for you do you have any suggestions for on how I can get this working? Can other PBXNSIP customers who are using ver 4.0.1.3442 test this to see if it's not just me that's having this problem. Thanks

Hi, We went from ver 4.0.1.3438 to 4.0.1.3442 and just noticed today that we can no longer do *67 and the number....it should pass the whole string to the dial plan but it doesn't anymore. If you have a number already in your address book with the *67 in the number it does work - like *6714166381234 the system will dial the complete number...but if you just pickup your phone and try to do *6714166381234 it reports back on the display not found and goes back to dial tone. Can this one be fixed ASAP as we have customers that were using this feature? Thanks

The passing of *67 to the dial plan is now broken in version 4.0.1.3442. I'll start a new thread.

I also tested this with the latest 4.0.1.3442 and the end user still can't change their web password.

I'm doing TAPI in V4 with a SNOM to TAPI software from http://www.xtelsio.com/ they also have other SIP to TAPI drivers/programs. They have a 30 day trial. It works really well. Our CRM software (web based) uses TAPI to auto load customer records when calls come in from the sales que, we also use it for outbound calls by just clicking on the telephone number in the CRM record.

Yes, for outbound trunk calls - but it did work in version 4.0.1.3440. I never tested it ext to ext. Thanks

The 30 seconds/6 rings then disconnect that was fixed/working in version 4.0.1.3440 is now not working in version 4.0.1.3442. Can anyone else confirm/test this? I made sure the new setting "Maximum ring duration" was set to 60 seconds - also made sure it was in my pbx.xml file - even restarted my system and call gets disconnected after 30 seconds/6 rings.

Mystery solved - why it was working for you and not me = a bug. I changed my codec to G711 and now I can do the *82 and *81 and it works - this means the system has a bug when using codec G729. Can you confirm this? Thanks.

We are using G729. Customer calls into the sales queue - agent takes the call - I can do *83 and listen in perfectly but when I try *82 or *81 I can hardley hear the 2 people talking - it's all distorted. I have all the right permissions in place. I even turned off call recording thinking that might be causing a problem but same results. How are you doing your testing? Meaning my phones are remote - not on the local lan - would that make a difference for your testing method? I'm also using SNOM 370's - would the calls be encrypted - would that make a difference? Our PBXNSIP is located in a data center. Thanks

We are now using version 4.0.1.3438 and are still having the same problem.

Hi pbx support, I started a new thread for this bug. http://forum.pbxnsip.com/index.php?showtopic=3407

Hi, I went from version 4.0.1.3438 to 4.0.1.3440 and now when someone leaves a user a voice mail message and the user goes to listen to it the system won't play the message. The message does get recorded because I can see it in the recordings directory and it does get emailed to the user. This is what it shows in my log when I try to play/listen to the message: [6] 2010/03/23 01:50:39: Sending RTP for 3c36d18e4fb0-q92iqzm3dvk7#776b6fae24 to myipaddress:62324 [8] 2010/03/23 01:50:41: Play audio_en/mb_number.wav [8] 2010/03/23 01:50:42: Play audio_en/bi_1.wav [8] 2010/03/23 01:50:42: Play recordings/msg221.wav [8] 2010/03/23 01:50:43: Play audio_en/mb_end_of_message.wav audio_en/mb_to_repeat.wav audio_en/bi_press_4.wav space5 audio_en/mb_to_delete.wav audio_en/bi_press_7.wav space5 audio_en/mb_to_help.wav audio_en/bi_press_0.wav space20 [9] 2010/03/23 01:50:43: SIP Rx tls:myipaddress:57066: When I try to listen to my message the system plays..."You have 1 new message, message number 1, end of message." In between the system prompts "message number 1" and "end of message" it should have played my message "msg221.wav" but it didn't. I made sure the "msg221.wav was in the recordings directory and I can manualy play it by copying the file from my Linux box to my Windows desktop and the message plays over Windows. I tested this with a bunch of different mail boxes and also created new mail boxes in version 4.0.1.3440 but I get the same results. Soon as I go back to version 4.0.1.3438 it starts working again and the log files look identical. Am I doing the upgrade properly? This is how I upgrade from version 4.0.1.3438 to 4.0.1.3440 1. Stop the pbx service 2. Rename pbxctrl to pbxctrl-3438 3. Rename pbxctrl-3440 to pbxctrl 4. Make sure the new pbxctrl is 755'd 5. Start the pbx service Am I missing any steps in the upgrade process? We really want to use version 4.0.1.3440 as it fixes a couple big bugs. Thanks

It happens with all users/mail boxes. Soon as we went back to version 4.0.1.3438 and tested it again it worked, so it looks like something in ver 4.0.1.3440 is causing the problem.

Hi pbxnsip, The 4.0.1.3440 does fix the 6 rings/30 disc propblem but that version introduces a new bigger bug - people calling into PBXNSIP can leave messages but when the mail box owner/user tries to listen to the messages it won't play the message....the message does get recorded because it also emails it - you just can't retrieve it from the phone. I had to go back to 4.0.1.3438

Hi pbx support, Did you have a chance to test this yet? Thanks

Hi pbxnsip, The system was a clean install of Linux 64 bit, then installed 4.0.1.3433.....but now at 4.0.1.3438 My html directory only has 1 file "helplinks.txt" and sub dir called img with my custom logo. My web browser does have Javascript enabled. Also tried 3 other computers with different browsers and same problem. Can you test version 4.0.1.3438.....login as end user and try changing your web password....it won't save for me. Thanks

That's great! Can you send me a link for a centos build?

Hi Bill H, I just went to the Registration page and I do see the LINES box but I don't have to put in a "1" because I just noticed below the LINES box is the "Enable Call Waiting: On Off" option. Wow, did they ever hide this option in a weird place. I'm using version 4.0.1.3438 not sure if you see the "Enable Call Waiting:" field in your version. This is great but would be better if the end user could pickup their phone and dial a * code to enable/disable. The end user can't even turn it on or off through their web browser, only admin can. Thanks for pointing me in the right direction.

Hi, Were using PBXNSIP 4.0.1.3438 centos I gave my customers a temp web password which they used to login to the GUI, then they try to change the password to something new but it doesn't work. The old password just sticks, entering a new password and saving it doesn't seem to work. I can login as admin and change it for them and the new one works but they should be able to do it. Is this a bug in version 4.0.1.3438? Thanks

Thanks, I'll take a look. So PBXNSIP doesn't have a * code to disable/enable call waiting? It would be great if they could add this feature so the end customer can control it. Most of our customers wouldn't know how to even get into their Linksys adapters.

Hi, Does anyone know how to disable the call waiting feature per extension? The extension is setup with a Linksys SPA2102 adapter. I can't seem to find any * codes that enables or disables call waiting for an extension. Thanks

In case anyone else is reading this - support advised me the system waits about 30 seconds and if doesn't get a answer/connect they disconnect the call - they will be making this a setting in the next release so we can give longer then 30 seconds before hanging up.

bump