Jump to content
Vodia PBX forum
R. Baltzer

Some problems with version 4.0.1.3499

Recommended Posts

Hi,

 

I have some PnP problems with the new version 4.0.1.3499, my Snom 300 and 320 (fw 8.2.29) phones are not provisioned correctly anymore:

 

I cannot set the VLAN ID anymore via the PBXNSIP webinterface, the field is gone on the PnP tab.

 

Also the Pin for Administrator is not working, it doesn't matter what is configured, the phone will be provisioned with "1234".

 

And even the web password needed for access to the Snom webinterface is not provisioned to the phone so I cannot access it anymore due to authentication failure. The password provisioned from the snom_3xx_phone.xml placed into the generated directory is not working to get webaccess to the phone...

 

The last thing I have noticed about provisioning is that the language on my phones is set to english, the phones are not picking up the dutch language anymore? When set logging to 8 I see the following error message in PBXNSIP:

[8] 2010/05/01 15:15:26: Received request for file snom/gui_lang_NL.xml

[8] 2010/05/01 15:15:26: Error finding snom/gui_lang_NL.xml, Send back 404 Not Found

And the files are still there...

 

Another problem with the assigned buttons is that the agent login/logout button is not working anymore.

With the 3.4 release of PBXNSIP this was a toggle button to login to or logout of the assigned agent group but now only the led is showing the status and the button is not working anymore. Using the star codes to login and logout is working fine, but the button does not.

 

Does anyone know how to handle these problems?

 

Kind regards,

 

Rene.

Share this post


Link to post
Share on other sites
I cannot set the VLAN ID anymore via the PBXNSIP webinterface, the field is gone on the PnP tab.

 

We decided to take this setting out, on purpose. The problem with provisioning the VLAN is that it is not the job of the PBX to provision that. For example, if the PBX would provision something like the DNS server or the netmask or even the IP address, chaos would be the result. For getting devices into certain VLAN, there are protocols like LLDP-MED or 802.1X. I know that only few phones can do this today; but we should not make the mistake to try to fix this problem with the provisioning.

 

Also the Pin for Administrator is not working, it doesn't matter what is configured, the phone will be provisioned with "1234".

 

The setting "admin_mode_password" is set by the PBX. The domain has a section for "Provisioning Parameters", where you can set the PIN for the phones. It would be better to have both a personal PIN and a administrator PIN (same for the phone web server password), so that the admin does not have to expose the password when a user wants to get on the phone web interface.

 

The point behind this is that there is a system administrator that has to manage a (potentially) large number of devices and cannot remember the PIN or password for each device. And he does not want end users screw up the phone configuration.

 

And even the web password needed for access to the Snom webinterface is not provisioned to the phone so I cannot access it anymore due to authentication failure. The password provisioned from the snom_3xx_phone.xml placed into the generated directory is not working to get webaccess to the phone...

 

See above. This is the "Authentication Password" of the domain.

 

The last thing I have noticed about provisioning is that the language on my phones is set to english, the phones are not picking up the dutch language anymore? When set logging to 8 I see the following error message in PBXNSIP:

[8] 2010/05/01 15:15:26: Received request for file snom/gui_lang_NL.xml

[8] 2010/05/01 15:15:26: Error finding snom/gui_lang_NL.xml, Send back 404 Not Found

And the files are still there...

 

Hmm. You mean you have this file in the html/snom directory? As far as a I can see it was included in the build process. But we might have to try this out here to see what the problem is.

 

Another problem with the assigned buttons is that the agent login/logout button is not working anymore.

With the 3.4 release of PBXNSIP this was a toggle button to login to or logout of the assigned agent group but now only the led is showing the status and the button is not working anymore. Using the star codes to login and logout is working fine, but the button does not.

 

The agent group login/logout behavior has slightly changed. Now you are logged in if you are on the list of agents, there is no extra flag for this in the extension any more (we had a lot of problems explaining what it means to be "logged in" in version 3). You need to specify per ACD who is allowed to "jump" in or out of the ACD. Maybe the agent was able to get out, but now cannot get in any more.

Share this post


Link to post
Share on other sites
Hmm. You mean you have this file in the html/snom directory? As far as a I can see it was included in the build process. But we might have to try this out here to see what the problem is.

 

Did you set the audio langauge to Dutch?

 

There was a mistake in the file snom_gui_lang.xml, copy the content below into the file html/snom_gui_lang.xml and then it should work.

 

<?xml version="1.0" encoding="utf-8" ?>
<gui-languages>
 <language url="{http-url snom}/gui_lang_DK.xml" name="Dansk"/>
 <language url="{http-url snom}/gui_lang_DE.xml" name="Deutsch"/>
 <language url="{http-url snom}/gui_lang_EN.xml" name="English"/>
 <language url="{http-url snom}/gui_lang_SP.xml" name="Espanol"/>
 <language url="{http-url snom}/gui_lang_FR.xml" name="Francais"/>
 <language url="{http-url snom}/gui_lang_IT.xml" name="Italiano"/>
 <language url="{http-url snom}/gui_lang_NL.xml" name="Nederlands"/>
 <language url="{http-url snom}/gui_lang_PL.xml" name="Polski"/>
 <language url="{http-url snom}/gui_lang_RU.xml" name="Russian"/>
 <language url="{http-url snom}/gui_lang_SW.xml" name="Svenska"/>
 <language url="{http-url snom}/gui_lang_TR.xml" name="Turkce"/>
</gui-languages>

 

Will be also fixed in the next build.

Share this post


Link to post
Share on other sites

I have a quick question....any help will be greatly appreciated.

 

In PBXnsip Release 4.1 on the admin guide on page (265 and 266) (under the "Assigning dollar amount to an Extension" section )

 

It states that if "credit for outbound calls" is left blank, it states that the user will be allowed unlimited calling. What happens if the amount hits zero? Also what if we want to revert to post paid. Would it not be better to have a field that you can check pre-paid and if yes, you are allowed to enter the credit for outbound calls.

 

Also how do we update the addition of credit automatically.

without having to enter it manually.

 

Also is there a way to authorize calls using an external server.

 

Thanks in advance for the help.

Share this post


Link to post
Share on other sites
It states that if "credit for outbound calls" is left blank, it states that the user will be allowed unlimited calling. What happens if the amount hits zero? Also what if we want to revert to post paid. Would it not be better to have a field that you can check pre-paid and if yes, you are allowed to enter the credit for outbound calls.

 

Can you open a new topic for that? I think it does not fit in this discussion thread. Thanks...

Share this post


Link to post
Share on other sites

Any help would greatly be appreciated. Thanks in advance.

 

 

Just loaded 4.0.1.3499 and now I am not able to call from an extension on one domain to a TN on another domain. I have multiple domains on one server. Any ideas?

Share this post


Link to post
Share on other sites
Just loaded 4.0.1.3499 and now I am not able to call from an extension on one domain to a TN on another domain. I have multiple domains on one server. Any ideas?

 

Roll back or roll forward... The 4.0.1.3499 has problems with the loopback detection. Send an email to support and you'll get a link to a newer version.

Share this post


Link to post
Share on other sites

×