Problem with v4.2.0.3981

[R. Baltzer]

Hi,

 

I have upgraded PBXnSIP version 4.2.0.3958 to the new version 4.2.0.3981 and now I have some provisioning problems:

 

My Snom 300 phones are not getting the configured function keys anymore (the phone is not picking up the config) and also the TFTP custom xml files (snom_300_custom.xml and snom_320_custom.xml) are not picked up by the Snom 300 and Snom 320 phones anymore.

 

I have reverted back to version 4.2.0.3958 and now PnP is working fine again.

 

My PnP config is based on the DHCP option 66 and my Snom phones have firmware version 8.4.27.

 

Could this be a bug in the new PBXnSIP version?

 

Kind regards,

 

Rene.

PS: I have posted this same question at http://forum.pbxnsip.com/index.php?/topic/4328-v42-first-update-available/

but there it is still unanswered.

[Vodia PBX]

http://forum.pbxnsip.com/index.php?app=forums&module=post&section=post&do=reply_post&f=14&t=4090&qpid=18723 deals with the same problem, but for snom 821.

[R. Baltzer]

http://forum.pbxnsip...4090&qpid=18723 deals with the same problem, but for snom 821.

 

 

Are you saying that this will be fixed in the next release or for now I have to create the link to the custom file myself?

 

Kind regards,

 

Rene.

[Vodia PBX]

If you want to have the custom file, you have to add the line yourself to the snom_821.xml file. Or you just edit the snom_820_phone.xml file (also through the web interface), and then there may be no need for a custom file at all.

[pbx support]

FYI...

 

http://wiki.snomone.com/index.php?title=PnP_Customization

[R. Baltzer]

FYI...

 

http://wiki.snomone....P_Customization

 

Ok, thanks, that's clear for now.

 

Still the problem remains about the Snom 300 function keys, they are not provisioned correctly anymore.

 

Kind regards,

 

Rene.

[pbx support]

Note that if you have button profile assigned to that extension, it will try to override the default assignment(snom_300_fkeys.xml). I think the extensions, be default, get assigned with the a "12 Buttons" profile, which would be wrong for a snom 300. So, can you please check if there is a wrong profile assigned?

[R. Baltzer]

Note that if you have button profile assigned to that extension, it will try to override the default assignment(snom_300_fkeys.xml). I think the extensions, be default, get assigned with the a "12 Buttons" profile, which would be wrong for a snom 300. So, can you please check if there is a wrong profile assigned?

 

Thanks for replying.

 

I understand that the assigned buttonprofile should overwrite the default button assignment, but that is my problem;

There are some Snom300 phones with assigned buttonprofiles and they still have the default Snom300 buttons.

So my guess was that the button assignment is not working.

Please note that the button assignment for my Snom320 phones is working fine, only the Snom300 phones are not getting the alternate defined buttons.

 

I have reverted back to PBXnSIP version 4.2.0.3958 and now also the buttons for the Snom300 phones are provisioned correctly again.

 

Kind regards,

 

Rene.