voipguy

Hi, We are using ver 4.0.1.3446, hotsted Pro +, G729 code, ccentos 64 bit . We customized PBXNSIP so were using our own logo at the very top and all the links etc refer back to our site, same with the copyright info. When you login as a user and select login type: Console Login it logs you in and you can see the new console screen but at the very top it displays PBXNSIP logo and info - it doesn't obey the customization settings that we enabled. Thanks

Hi pbxnsip, Did this ever work in ver 3.4 or earlier? If not then PBXNSIP needs to update their web site sales info/documents letting potential customers know that *81 and *82 are currently only supported if useing codec G711 before they invest thousands of dollars in this software like I did. This is going to be a major problem for us until version 4 supports *81 and *82. We use the hosted version and there's no way we will sign up customers for a call centre and use codec G711 - too much bandwidth.

Is there a fix for this yet? I'm using ver 4.0.1.3446 and this bug still exists. I'm using the G729 codec. Thanks,

Hi pbxnsip, The *67 topic is perfectly clear. I don't have a problem with the whole *67 topic....I'm just trying to put together this dialing plan. If you don't know how to do the requested dial plan entry then please just let me know so I can move on and maybe I'll contact someone else in PBXNSIP to find the answer. Thanks.

PBXNSIP...do you know how to create this dial plan? Thanks

Hi pbxnsip, I'm aware of the other thread regarding the *67, I was apart of it. I don't see any problems with the *67 design. This is not an issue - we use a proxy server - if we were going to terminate the call on a FXO gateway then we wouldn't strip the *67 - we would send the whole *67NUMBER to the FXO gateway - then the FXO line would block the caller id. Since PBXNSIP modified it's code per the other thread - the PBXNSIP doesn't think it's a star code because we removed the feature code 67 from the feature list - when the extension or SIP phone dials *67NUMBER the PBXNSIP knows *67 is not a feature code anymore so send the whole string to the dialplan. We are useing the hosted version of PBXNSIP - we can't have PBXNSIP block the call then send it to our proxy server because then our proxy server doesn't know who to bill for the call - but if PBXNSIP doesn't block the call and sends our proxy server the whole string *67NUMBER then our proxy server knows to block the number before sending to the destination provider or if sending call to a FXO gateway send the *67NUMBER. The pattern and replacement you provided doesn't do what I'm asking for - if the user only enters *67 and 7 digits then we want the replacement to add default areacode 416 after the *67 - so if user dials *676381234 we want PBXNSIP to send *674166381234. Now if the user dialed more then 7 digits after the *67 then just send whatever they entered and don't prefix with 416. This would probally need two entries in the dial plan but I'm not sure what they would be. Right now we allow 7 digit dialing but always send at least 10 digits to the proxy server. This is the dial plan that allows 7 digit dialing but we don't know how to also make it work if user enters *67. 7 digit dialing Pattern: 2xxxxxx|3xxxxxx|4xxxxxx|5xxxxxx|6xxxxxx|7xxxxxx|8xxxxxx|9xxxxxx| Replacement: 416* Now if user picks up phone and dials 6381234 the above dial plan will send 4166381234 Now how do we do this with *67 ? if they dial *676381234 we want to send *674166381234 Thanks Thanks

Hi pbxnsip, I don't understand your response? We do use *67 for indicating anonymous calls. If a customer wants to call a telephone number but not have his number show up on the destinations call display phone then my customer picks up the phone and dials the number like this *6714166381234 and PBXNSIP sends *6714166381234 to my proxy server - my proxy server see's the *67 and then changes the customers out going call display name and number to anonymous and then dials the destination number 14166381234 and on that persons call display phone it shows anonymous or private name private number. Does anyone know how to create the dial plan in my first post? Thanks

Hi, We are using version 4.0.1.3446, centos linux 64 bit. In our dial plan we have: Pattern: \*([0-9]*)@.* Replacement: sip:*\1@\d;user=phone We also made sure feature code 67 is not being used. If the customer only dials a local 7 digit number 638-1234 we want to add a default prefix of 416 so the dial plan sends to our proxy server 4166381234 but we don't know how to do this when the customer uses *67. So if a customer just enters *676381234 how do we get the dialplan to send *674166381234 to our proxy server? Now here's the second part - if the customer enters more then 7 digits after the *67 then we don't want to prefix it with 416 in the replacement, we just want to send what ever they entered. So if they dial *6716046381234 the dial plan would send *6716046381234 to our proxy server the same thing if they dial *679056381234 we want the dial plan to send *679056381234 to our proxy server. Basicaly anything entered that's greater then 7 digits after the *67 then don't add the default 416 prefix, just send what they entered. Anyone know how to do this? Thanks

Yea, I made sure before I did all my testing that I put my ip address in the authorized/allow list.

Hi pbxnsip, Thanks for the quick reply. I got it working this morning. I couldn't figure out why it was only generating 3 files and those 3 files were downloading to the phone but when it got to the 3xx_phone.xml file it wouldn't download - then I noticed the first 3 files get downloaded via port 80 and then the rest go by port 443 - port 443 was blocked in my firewall. About 2 weeks ago we turned the box into a Linux 64 bit and forgot to open that port. It all works now. version 4.0.1.3446 is working really well. Thanks

Hi, I'm running PBXNSIP 4.0.1.3446 on centos 64 bit. I decided to setup my buttons on my SNOM370 phone - now the phone won't even download it's settings from PBXNSIP. It never did work properly but today I decided to try and understand the whole PNP. I now don't have a phone to use. I don't think it's a username or password issue. I actually made my web/sip/admin password all the same for testing purposes. My log from PBXNSIP: [9] 2010/03/28 18:19:04: Received request for file snom370.htm [9] 2010/03/28 18:19:04: PnP file is snom_370.xml [9] 2010/03/28 18:19:04: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:09: No authintication info found. Challenge the sender [9] 2010/03/28 18:19:09: Remote site (my ip address) closed the connection [9] 2010/03/28 18:19:09: Received request for file snom370.htm [9] 2010/03/28 18:19:09: PnP file is snom_370.xml [9] 2010/03/28 18:19:09: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:09: Sending xml config file snom_370.xml [9] 2010/03/28 18:19:09: Remote site (my ip address) closed the connection [9] 2010/03/28 18:19:09: Received request for file snom370-000413269774.htm [9] 2010/03/28 18:19:09: PnP file is snom_3xx.xml [9] 2010/03/28 18:19:09: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:15: No authintication info found. Challenge the sender [9] 2010/03/28 18:19:15: Remote site (my ip address) closed the connection [9] 2010/03/28 18:19:15: Received request for file snom370-000413269774.htm [9] 2010/03/28 18:19:15: PnP file is snom_3xx.xml [9] 2010/03/28 18:19:15: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:15: Sending xml config file snom_3xx.xml [9] 2010/03/28 18:19:15: Remote site (my ip address) closed the connection [9] 2010/03/28 18:19:15: Received request for file snom_3xx_fw.xml [9] 2010/03/28 18:19:15: PnP file is snom_3xx_fw.xml [9] 2010/03/28 18:19:15: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:20: No authintication info found. Challenge the sender [9] 2010/03/28 18:19:20: Remote site (my ip address) closed the connection [9] 2010/03/28 18:19:20: Received request for file snom_3xx_fw.xml [9] 2010/03/28 18:19:20: PnP file is snom_3xx_fw.xml [9] 2010/03/28 18:19:20: Either trust mac is off OR mac is not with any user. Looking for auth info... [9] 2010/03/28 18:19:20: Sending xml config file snom_3xx_fw.xml [9] 2010/03/28 18:19:20: Remote site (my ip address) closed the connection My SNOM370 log: [5] 24/12/2001 00:00:54: webclient::handle_challenge: resending request ! [6] 24/12/2001 00:00:54: webclient::resend_request: GET /provisioning/snom370.htm HTTP/1.1 Host: (my PBXNSIP ip address) Authorization: Basic MjI0QGN3Yy5jd2N2b2lwLmNvbTpwYXNzd29yZA== Accept-Language: en Connection: Keep-Alive Keep-Alive: 5 User-Agent: Mozilla/4.0 (compatible; snom370-SIP 8.2.25 1.1.3-s) [7] 24/12/2001 00:00:54: Conf setup: code: 200, host: (my PBXNSIP ip address):80, file: /provisioning/snom370.htm [5] 24/12/2001 00:00:54: read_xml_settings: found setting-files XML header [5] 24/12/2001 00:00:54: read_xml_settings: found one byte encoding: 1 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: http://(my PBXNSIP ip address):80/prov/snom_3xx_fw.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_dialplan_empty.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_fkeys.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/prov/snom_web_lang.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/prov/snom_gui_lang.xml?model=snom370 [5] 24/12/2001 00:00:54: read_setting_file_list: added URL: https://(my PBXNSIP ip address):443/tftp/snom_370_custom.xml [5] 24/12/2001 00:00:54: Conf setup: found xml style settings [5] 24/12/2001 00:00:54: Fetching URL: http://(my PBXNSIP ip address)/provisioning/snom370-000413269774.htm [5] 24/12/2001 00:00:59: webclient::handle_challenge: http server is asking for credentials! [5] 24/12/2001 00:00:59: webclient::handle_challenge: resending request ! [6] 24/12/2001 00:00:59: webclient::resend_request: GET /provisioning/snom370-000413269774.htm HTTP/1.1 Host: (my PBXNSIP ip address) Authorization: Basic MjI0QGN3Yy5jd2N2b2lwLmNvbTpwYXNzd29yZA== Accept-Language: en Connection: Keep-Alive Keep-Alive: 5 User-Agent: Mozilla/4.0 (compatible; snom370-SIP 8.2.25 1.1.3-s) [7] 24/12/2001 00:00:59: Conf setup: code: 200, host: (my PBXNSIP ip address):80, file: /provisioning/snom370-000413269774.htm [5] 24/12/2001 00:00:59: read_xml_settings: found setting-files XML header [5] 24/12/2001 00:00:59: read_xml_settings: found one byte encoding: 1 [5] 24/12/2001 00:00:59: Conf setup: found xml style settings [5] 24/12/2001 00:00:59: Fetching URL: http://(my PBXNSIP ip address):80/prov/snom_3xx_fw.xml?model=snom370 [5] 24/12/2001 00:01:04: webclient::handle_challenge: http server is asking for credentials! [5] 24/12/2001 00:01:04: webclient::handle_challenge: resending request ! [6] 24/12/2001 00:01:04: webclient::resend_request: GET /prov/snom_3xx_fw.xml?model=snom370 HTTP/1.1 Host: (my PBXNSIP ip address) Authorization: Basic MjI0QGN3Yy5jd2N2b2lwLmNvbTpwYXNzd29yZA== Accept-Language: en Connection: Keep-Alive Keep-Alive: 5 User-Agent: Mozilla/4.0 (compatible; snom370-SIP 8.2.25 1.1.3-s) [7] 24/12/2001 00:01:04: Conf setup: code: 200, host: (my PBXNSIP ip address):80, file: /prov/snom_3xx_fw.xml?model=snom370 [5] 24/12/2001 00:01:04: read_xml_settings: found phone-settings XML header [5] 24/12/2001 00:01:04: read_xml_settings: found one byte encoding: 1 [5] 24/12/2001 00:01:04: Conf setup: found xml style settings [5] 24/12/2001 00:01:04: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [7] 24/12/2001 00:01:04: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:04: Conf setup: return code 500; requeueing >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370<; attempt: 1, state: 32 [5] 24/12/2001 00:01:07: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [9] 24/12/2001 00:01:07: Timer: gui/gui_appear.cpp (5842): [set_display_light] [7] 24/12/2001 00:01:08: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:08: Conf setup: return code 500; requeueing >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370<; attempt: 2, state: 32 [5] 24/12/2001 00:01:11: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [7] 24/12/2001 00:01:11: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:11: Conf setup: return code 500; requeueing >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370<; attempt: 3, state: 32 [5] 24/12/2001 00:01:14: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [7] 24/12/2001 00:01:14: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:14: Conf setup: return code 500; requeueing >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370<; attempt: 4, state: 32 [5] 24/12/2001 00:01:17: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [7] 24/12/2001 00:01:17: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:17: Conf setup: return code 500; requeueing >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370<; attempt: 5, state: 32 [5] 24/12/2001 00:01:20: Fetching URL: https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370 [8] 24/12/2001 00:01:20: Sending Keepalive to Watchdog [7] 24/12/2001 00:01:20: Conf setup: code: 500, host: (my PBXNSIP ip address):443, file: /prov/snom_3xx_phone.xml?model=snom370 [5] 24/12/2001 00:01:20: Conf setup: return code 500; giving up on >https://(my PBXNSIP ip address):443/prov/snom_3xx_phone.xml?model=snom370< [6] 24/12/2001 00:01:20: WEBSV: init() is_initialised: 0 [6] 24/12/2001 00:01:20: WEBSV: Close port 0 [6] 24/12/2001 00:01:20: WEBSV: Open port 80 [6] 24/12/2001 00:01:20: WEBSV: Close port 0 [6] 24/12/2001 00:01:20: WEBSV: Open port 443 I see the SNOM370 phone is getting a 500 error code? I reset my SNOM370 back to factory defaults. I deleted all files in that extensions generated folder, same with the tftp folder, still doesn't work. Any ideas on how I can get my phone back up and running? Thanks,

running version 4.0.1.3446 and it fixes the problem. Thanks

Thanks. I tested it and it works great.

Hi nexSIP, It takes 2 tries for me when I try to start 4.0.1.3442. I was told with this version it's a delayed start because it now first loads the CDR's. version 4.0.1.3446 can be found here: http://pbxnsip.com/protect/pbxctrl-centos5-4.0.1.3446 I tested it and it fixes a few things. 1. the 30 second/6 ring disconnect issue 2. you can now login with just the 10 digit telephone number and password....you don't need the @domain. 3. the end user can now change their own web password 4. looks like the missed calls tab now displays missed calls. (still buggy) 5. plus a few GUI changes It took me 2 starts before the ap would load. 4.0.1.3446 is looking great so far.

I'm using Linux 64 bit OS and donwloaded the PBXNSIP Centos 4.0.1.3442 from pbxnsip.com so I'm not sure if the 4.0.1.3442 was 32 bit or 64 bit. Maybe that could have been the problem? Did you guys ever put out a 64 bit pbxnsip centos version before?

ok that explains the slow startup. We have less then 30 connections (HTTP or SIP)....so that definitly wasn't the problem. We are using Linux 64 bit. Can you release the download links so I can test this weekend? Thanks

That's great news.....can you post a link to version 4.0.1.3445 ? Thanks

I know were still in beta and I was running the latest ver 4.0.1.3442 but after 3 days it just crashed 5 minutes ago. I noticed with this version when I try to start the service it takes a few trys before it loads - very strange - other versions don't have this startup problem - anyway 3 days later (today) it just wouldn't respond - I could see the service was still running but no phones could register and the web interface would not load/respond. I recommend going back to version 4.0.1.3438, if your only running G711 then ver 4.0.1.3440 works as well.

1 caller in Sales Queue talking to 1 agent and then I was trying to do the *81 or *82 - that's all the people at the time on the system. I never looked at the CPU level at that time but it's never high - like less then 5%.

For anyone else reading this - pbxnsip confirmed this is a bug - when you have it set to not allow a user to change their SIP password it also prevents them from changing their WEB password - even if you have it set to allow them to change their WEB password. It will be fixed in a future release.

For anyone else reading this - PBXNSIP confirmed this is a bug and will be fixed in future release.

Hi pbx support, I created a ticket in your system....ticket ID: YST-152607 In the ticket I put in a test login account for you to try. Please login into my system with the login details I provided and change your web password - if it doesn't change for you then that means it's not my desktop computer or web browsers that are causing the problem. Thanks,

version 4.0.1.3442 fixed this problem - they didn't say but I believe it was a codec problem in version 4.0.1.3440.

I got it working - what I did was switch the dial plan to text mode - copied it all...then deleted that dial plan - created a new dial plan with same text - now it works.

I got it working - what I did was switch the dial plan to text mode - copied it all...then deleted that dial plan - created a new dial plan with same text - now it works.