3.3.0

[Vodia PBX]

We have made new builds in the version 3 of the PBX:

 

http://pbxnsip.com/download/pbxctrl-3.3.0.3165.exe (Windows Upgrade)

http://pbxnsip.com/download/pbx3.3.0.3165.exe (Windows Full Install)

http://pbxnsip.com/download/pbxctrl-freebsd7.0-3.3.0.3165 (FreeBSD 7 32 bit)

http://pbxnsip.com/download/pbxctrl-centos5-3.3.0.3165 (CentOS 5.2)

http://pbxnsip.com/download/pbxctrl-suse10-3.3.0.3165 (SuSE10, 32 bit)

http://pbxnsip.com/download/pbxctrl-rhes4-3.3.0.3165 (RedHat EL4)

http://pbxnsip.com/download/pbxctrl-debian4.0-3.3.0.3165 (Debian 4.0)

http://pbxnsip.com/download/pbx-darwin9.0-3.3.0.3165.zip (MacOS)

http://pbxnsip.com/cs410/update-3.3.0.3165.tgz (CS410)

This release has no major changes, just a lot of "smaller" things that we cleaned up or fixed since the 3.2 version. I believe it should be a great version, pretty stable, doing 99 % of what business expect today from an IP-PBX. I know some of you want to see a couple of new features like full video support and attended transfer into anything; we'll do this in a new version 4. Until then it is good to have a stable version 3.

 

Release Notes are as usual at http://wiki.pbxnsip.com/index.php/Release_Notes_3.3. If you are running 3.2 or 3.1, IMHO it should be an easy upgrade. As always, when you upgrade this is a excellent opportunity to back up the working directory before upgrading and store it in a safe place.

 

If you are upgrading from previous versions and you are in North America (country code "1"), make sure that the dial plans use the 10-digit notation. For outbound calls, you can also tell the trunk on how the number should be represented. That seems to be the biggest problem with upgrades so far.

 

[Carl Johnson]

v3.3.0.3163 - PNP Polycom

 

PNP quit working for our Polycoms in 3163 .. the system now will not provision for internal or external extensions .. we use the MAC address setup in the Reg tab for inside phones via TFTP and on the outside Auth with the phone ID and pass via HTTP. Here is an example of the logfile the phone leaves .. trimmed a little to show relevant info. Checked the generated dirs after removing the previous files and they are MIA .. PLEASE HELP!! Checked that we have a PNP file defined in /html/pnp.xml and we do??

 

PBXNSIP: [8] 2009/03/17 16:06:20: Could not identify phone vendor for MAC 0004F20600FC

 

Phone:

 

0317220347|copy |3|02|'tftp://192.168.40.223/000000000000.cfg' from '192.168.40.223'

0317220347|copy |3|02|TFTP download error

0317220347|copy |3|02|tftpLib error: tftp transfer failed: error 0x4b0008

0317220347|copy |4|02|Download of '000000000000.cfg' FAILED on attempt 1

0317220347|copy |3|02|Update of '/ffs0/init.mac' failed, leaving local copy intact

0317220347|cfg |5|02|Prm|Updating 000000000000.cfg failed

0317220347|cfg |3|02|Prm|Download of MAC.cfg failed

0317220347|cfg |3|02|Prm|Trying to boot from existing configuration

0317220347|cfg |3|02|Prm|Booting from existing configuration

0317220347|cfg |*|02|Prm|Configuration file "polycom_phone_0004F20600FC.cfg" is from template Unknown, revision Unknown

0317220347|cfg |*|02|Prm|Configuration file "polycom_phone_0004F20600FC.cfg" SHA1 digest: 736BD17BF4C1A24F1505B0522C63B890D30631C3

0317220347|cfg |*|02|Prm|Configuration file "polycom_sip_0004F20600FC.cfg" is from template sip.cfg, revision 1.417.2.26

0317220347|cfg |*|02|Prm|Configuration file "polycom_sip_0004F20600FC.cfg" SHA1 digest: 22E6A12FAC97955C92775379541F1A9A2572B144

0317220347|so |3|02|Success provisioning.

0317220347|so |*|02|Configuration files: http://192.168.40.223:80/provisioning/poly...004F20600FC.cfg, http://192.168.40.223:80/provisioning/poly...004F20600FC.cfg

0317220347|copy |3|02|'tftp://192.168.40.223/0004f20600fc-phone.cfg' from '192.168.40.223'

0317220347|copy |3|02|TFTP download error

0317220347|copy |3|02|tftpLib error: tftp transfer failed: error 0x4b0008

0317220347|copy |4|02|Download of '0004f20600fc-phone.cfg' FAILED on attempt 1

[Carl Johnson]

One other note .. all PNP settings are missing in the webgui .. but the file is in place?

[Vodia PBX]

Checked that we have a PNP file defined in /html/pnp.xml and we do??

 

PBXNSIP: [8] 2009/03/17 16:06:20: Could not identify phone vendor for MAC 0004F20600FC

 

Remove the pnp.xml file or merge it with the attached one.

pnp.xml

[Carl Johnson]

Cannot provision Polycom using 3.3.0.3165 with HTTP using auth. It is odd as the phone can upload the log files via HTTP to the system but not provision, we are using SIP replacements as well for the DMZ? Internal phones will provision via TFTP correctly.

 

[6] 2009/03/18 10:55:02: HTTP Request tftp/2345-11402-001.bootrom.ld

[9] 2009/03/18 10:55:02: Remote site closed the connection

[9] 2009/03/18 10:55:26: Last message repeated 3 times

[6] 2009/03/18 10:55:26: PnP: Receive 0004f210d648-boot.log:

 

** modified the real world IP address to the word DMZIP **

 

0219185249|copy |3|00|'http://180%40rcp.local:****@IP/2345-11402-001.bootrom.ld' from 'DMZIP'

0219185255|cfg |3|00|Image 2345-11402-001.bootrom.ld has not changed

0219185255|copy |3|00|buffered_write: transfer Terminated on entry. Return 0

0219185255|copy |3|00|Download of '2345-11402-001.bootrom.ld' succeeded on attempt 1 (addr 1 of 1)

0219185255|cfg |3|00|Downloaded bootROM is identical to current version 4.1.2

0219185255|copy |3|00|'http://180%40rcp.local:****@IP/0004f210d648.cfg' from 'DMZIP'

0219185300|copy |4|00|Download of '0004f210d648.cfg' FAILED on attempt 1 (addr 1 of 1)

0219185300|copy |3|00|transport res: 22 respCode 401

0219185300|copy |3|00|transport error: Curl Error strings have been compiled out.

0219185300|copy |3|00|transport error buffer: The requested URL returned error: 401.

0219185300|copy |3|00|Update of '/ffs0/init.mac' failed, leaving local copy intact

0219185300|copy |3|00|'http://180%40rcp.local:****@DMZIP/000000000000.cfg' from 'DMZIP'

0219185300|copy |4|00|Download of '000000000000.cfg' FAILED on attempt 1 (addr 1 of 1)

0219185300|copy |4|00|Server 'DMZIP' said '000000000000.cfg' is not present

0219185300|copy |3|00|Update of '/ffs0/init.mac' failed, leaving local copy intact

0219185300|cfg |5|00|Updating 000000000000.cfg failed

0219185300|cfg |3|00|Download of MAC.cfg failed

0219185300|cfg |3|00|Trying to boot from existing configuration

0219185300|cfg |4|00|Can't boot: MAC.cfg is not present

0219185310|app1 |6|00|0004f210d648.cfg

0219185310|app1 |6|00|Uploading boot log, time is THU FEB 19 18:53:10 2009

[Vodia PBX]

0219185300|copy |3|00|transport error buffer: The requested URL returned error: 401.

 

That looks like a username/password mismatch to me. Make sure that the username is in the format user@domain and the password is really really correct.

[hosted]

Man this is going to be a major undertaking to upgrade from 3.01 with all those PNP setting...

[R. Baltzer]

Goodmorning,

 

I have a problem too with my PNP configuration, now with version 3.3 it is not working anymore.

 

My situation:

I have a LAN with dhcp (and option 66 configured to the PBX) and a VLAN also with dhcp (with option 66 again pointing to the PBX). Within PBXNSIP the setting “Listen to sip.mcast.net” is turned off and TFTP access was possible unsecured.

With pbxnsip version 3.2 a phone gets an ip-adres from my LAN and finds the PBX. Then it gets the configuration and firmware and switches after rebooting to my VLAN and all was working fine.

I have also placed some xml files into the html directory for settings that were not provisioned by pbxnsip.

I have noticed that after upgrading to version 3.3.0.3165 my PNP is not working until I remove all the xml files on my html directory but then my phones do nat change to my VLAN anymore. Also the dutch language is not available anymore for my snom 300 and 320 phones (firmware 7.3.14) and the dialtone is not dutch.

 

What would be the best solution to get PNP working again?

 

Kind regards,

 

Rene.

[Vodia PBX]

What would be the best solution to get PNP working again?

 

If you changed your pnp.xml file, check the pnp file in this post for changes.

 

The pnp had to be updated because it was in many cases too easy to get a configuration from any web browser in the LAN or even the WAN.

 

I know this is a pain for many people who had their own pnp.xml file.

 

Of course our intention is that there is no need to have any changes in pnp any more.

[R. Baltzer]

If you changed your pnp.xml file, check the pnp file in this post for changes.

 

The pnp had to be updated because it was in many cases too easy to get a configuration from any web browser in the LAN or even the WAN.

 

I know this is a pain for many people who had their own pnp.xml file.

 

Of course our intention is that there is no need to have any changes in pnp any more.

 

I am not using a modified pnp.xml file so that should be no problem in my case.

But as I described my situation, Listen to sip.mcast.net = off and Dhcp option 66 within the LAN and the VLAN, should PNP be working?

Or is it configured like that only possible to provision with usernames and passwords on the phones?

 

What would be the best solution to autoprovision without user interaction on the phones?

 

Kind regards,

 

Rene.

[Vodia PBX]

I am not using a modified pnp.xml file so that should be no problem in my case.

But as I described my situation, Listen to sip.mcast.net = off and Dhcp option 66 within the LAN and the VLAN, should PNP be working?

Or is it configured like that only possible to provision with usernames and passwords on the phones?

 

What would be the best solution to autoprovision without user interaction on the phones?

 

Okay, I tried that out here. That setup is what also used and that is what I would also recommend.

 

For me it worked. I had some trouble with the VLAN setup, the Ethernet switch was a little bit bitchy and I forgot to bind the tftp port also on the VLAN interface. But then it worked smoothly. There is one more thing that could be a problem, it is that the phone may need an extra reboot cycle after receiving the VLAN ID.

[R. Baltzer]

Okay, I tried that out here. That setup is what also used and that is what I would also recommend.

 

For me it worked. I had some trouble with the VLAN setup, the Ethernet switch was a little bit bitchy and I forgot to bind the tftp port also on the VLAN interface. But then it worked smoothly. There is one more thing that could be a problem, it is that the phone may need an extra reboot cycle after receiving the VLAN ID.

 

Ok, thanks, I will try again.

 

Can I still put extra xml files for additional snom settings in the html directory?

And to get the dutch language on my snom phones, do I still have to place these extra files in the html directory?

 

Kind regards,

 

Rene.

[Carl Johnson]

That was the first item validated and they are correct and match, but will not work .. I can logon to the web GUI with the username/password combo so it is good?

[Vodia PBX]

Can I still put extra xml files for additional snom settings in the html directory?

And to get the dutch language on my snom phones, do I still have to place these extra files in the html directory?

 

Yes, you can still put extra files there, but now the name must be snom_320_custom.xml (replace 320 with the model).

 

I guess I should just try to provision a phone in Dutch and see what happens...

[Carl Johnson]

Please address the PNP issue as shown above .. as noted the username/password have been validated on the phone and pbx and it will NOT provision phones via HTTP using a username/password combo??

[Carl Johnson]

Another note on this .. after looking at the logs .. it appears the phone is looking for the wrong URL, why would this be the case if I can authenticate with the PBX ..

 

it is trying:

 

http://DMZIP/0004f210d648.cfg

 

should be going to:

 

http://DMZIP/provisioning/0004f210d648.cfg

 

as that URL does work with that user/pass .. is the PBX just broken as the PNP wiki stuff notes it should do that in succession .. correct?

[R. Baltzer]

Yes, you can still put extra files there, but now the name must be snom_320_custom.xml (replace 320 with the model).

 

I guess I should just try to provision a phone in Dutch and see what happens...

 

That would be very nice if you want to test that for me.

 

Kind regards,

 

Rene.

[Vodia PBX]

That would be very nice if you want to test that for me.

 

Looks like there was a gremlin in the provisioning of the language... I guess we have to put this into a 3.3.1.

[R. Baltzer]

Looks like there was a gremlin in the provisioning of the language... I guess we have to put this into a 3.3.1.

 

Ok, thanks.

When do you expect this new release to be ready?

 

Kind regards,

 

Rene.

[Vodia PBX]

When do you expect this new release to be ready?

 

Beginning of next week.

[R. Baltzer]

Beginning of next week.

 

Perfect, thanks a lot !

 

Have a nice weekend.

 

Rene.

[Carl Johnson]

Please address the HTTP provisiong issue stated here and above in this post.

 

Another note on this .. after looking at the logs .. it appears the phone is looking for the wrong URL, why would this be the case if I can authenticate with the PBX ..

 

it is trying:

 

http://DMZIP/0004f210d648.cfg

 

should be going to:

 

http://DMZIP/provisioning/0004f210d648.cfg

 

as that URL does work with that user/pass .. is the PBX just broken as the PNP wiki stuff notes it should do that in succession .. correct?

[Vodia PBX]

Please address the HTTP provisiong issue stated here and above in this post.

 

Can you start a new thread...? Things get messy in this thread... 3.3.1 is already in the pipeline.

[eHans]

Our pbx is attached to two Vegastream PSTN ISDN Gateways (Vega 50 6x4). The gatewas are connected to another phone system. So we have to dial a "0" for acces to the public telephone network.

 

After upgrading to Version 3.3.0.3165 (Win32) we have the following problem: when dialing a local phone number (for example 0 12345) we get no connection. When we include the area code (for example 0 02204 12345) everything works.

 

With version 3.2.0 everything was fine. We didn't change anything in the trunk settings for the dial plans. Any ideas / suggestions?

 

Here are excerpts from the logs:

 

pbx:

 

[5] 2009/04/02 14:35:09: Dialplan Default: Match 083417@sip.oevermann.de to <sip:083417@192.168.232.25> on trunk VEGA02

[5] 2009/04/02 14:35:12: BYE Response: Terminate 3c2693b1753c-dppgy7zcontc

 

 

Vega:

 

2009-04-02 14:35:09 Daemon.Info 192.168.232.25 Apr 2 15:35:09 vega02.sip.oevermann.de ROUTER : LOG: 02/04/2009 15:35:09.550 ROUTER (I)R0bC00 FINDROUTE profile:2(LAN_to_ISDN) plan:6<010> call ref=[f15b0117] <-- SIP [2,1] dest=NAME:0,TEL:0 <010> --> ISDN [4,1] dest=TEL:0,TELC:4461

2009-04-02 14:35:09 Daemon.Info 192.168.232.25 Apr 2 15:35:09 vega02.sip.oevermann.de ROUTER : LOG: 02/04/2009 15:35:09.552 ROUTER (I)R0bC00 call proceeding<010> call ref=[f15b0117]

2009-04-02 14:35:09 Daemon.Info 192.168.232.25 Apr 2 15:35:09 vega02.sip.oevermann.de ISDN : LOG: 02/04/2009 15:35:09.570 ISDN (I)R02C08 outgoing<010> call ref=[f15b0117] dest=TEL:0,TELC:4461

2009-04-02 14:35:09 Daemon.Info 192.168.232.25 Apr 2 15:35:09 vega02.sip.oevermann.de ISDN : LOG: 02/04/2009 15:35:09.730 ISDN (I)R03C08 connect g711Alaw64k<010> call ref=[f15b0117]

2009-04-02 14:35:10 Daemon.Info 192.168.232.25 Apr 2 15:35:09 vega02.sip.oevermann.de SIP : LOG: 02/04/2009 15:35:09.815 SIP (I)R03C44 connect g711Alaw64k (Profile - Data)<010> call ref=[00000000]

2009-04-02 14:35:12 Daemon.Info 192.168.232.25 Apr 2 15:35:12 vega02.sip.oevermann.de ISDN : LOG: 02/04/2009 15:35:12.380 ISDN (I)R04C08 disconnect 16<010> call ref=[f15b0117]

2009-04-02 14:35:12 Daemon.Info 192.168.232.25 Apr 2 15:35:12 vega02.sip.oevermann.de ISDN : LOG: 02/04/2009 15:35:12.380 ISDN (I)R04C08 send release 16<010> call ref=[f15b0117]

2009-04-02 14:35:12 Daemon.Info 192.168.232.25 Apr 2 15:35:12 vega02.sip.oevermann.de SIP : LOG: 02/04/2009 15:35:12.387 SIP (I)R04C44 disconnect(disc req) 16<010> call ref=[f15b0117]

[Vodia PBX]

Our pbx is attached to two Vegastream PSTN ISDN Gateways (Vega 50 6x4). The gatewas are connected to another phone system. So we have to dial a "0" for acces to the public telephone network.

 

After upgrading to Version 3.3.0.3165 (Win32) we have the following problem: when dialing a local phone number (for example 0 12345) we get no connection. When we include the area code (for example 0 02204 12345) everything works.

 

With version 3.2.0 everything was fine. We didn't change anything in the trunk settings for the dial plans. Any ideas / suggestions?

 

Here are excerpts from the logs:

 

Did you set the country code to 49? If yes, then check the dial plan again. The patterns in entries there should *not* have prefixes. You can add prefixes in the replacement, but the PBX internally puts everything into a global format, which starts with 00CCAA (CC=country code, AA=area code) or 0AA or just the local number (the way you would write a number down on paper).

 

For example, you could use pattern 0033*, and replacement 00033* if you want to put a zero before the number if you want to have a rule for France.