R. Baltzer
-
Posts
75 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by R. Baltzer
-
-
Beginning of next week.
Perfect, thanks a lot !
Have a nice weekend.
Rene.
-
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.
-
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.
-
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.
-
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.
-
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.
-
In version 3.2, it is 7.1.39. In version 3.3, we'll switch to version 7.3.14. The 7.3.14 version requires a different way of provisioning, some details have changed (e.g. the enabling of the intercom feature).
Thanks a lot for your reply.
Can you tell me when to expect this version 3.3 ?
All my phones are already on the 7.3.14 firmware so then I know if it would be better to wait for version 3.3 or to downgrade all my phones to firmware 7.1.39.
Kind regards,
Rene.
-
Hi,
Is there anybody who can tell me what Snom 300 and Snom 320 firmware would be the best when using with PBXNSIP 3.2.0.3143 ?
Should I use Snom firmware 7.3.14 or is better to use firmware 7.1.39 and can you tell me why ?
Have a nice weekend!
Rene.
-
What phone type? What firmware?
I am using snom phones, type 300 and 320.
Firmware version 7.3.14 (previous version 7.3.11a makes no difference)
Kind regards,
Rene.
-
HI;
has anyone had an issue where they are on the phone and they continually hear DTMF tones when noone is pressing any buttons?
pls advise
I have the same problem too.
Sometimes wy users are hearing fully random dtmf tones during the conversation without anyone pressing a button.
Kind regards,
Rene.
-
just installed 3.1.1.3101
...now the logon/logoff buttons and lamps are not working anymore on my snom 320 phones.
also the DND toggle buttons are not working anymore.
any ideas?
I have reverted back to 3.1.1.3100 and now the buttons are working again.
Kind regards,
Rene
-
Hi,
I have noticed that all the agents are still able to logout from an agent group even when I have set that at least one agent should remain in the group. It looks like these functionality is not working.
And there is also still the strange call transfer behavior described in http://forum.pbxnsip.com/index.php?showtop...entry6766
After transfering the call the call is connected but pbxnsip is thinking that the call is put on hold.
Kind regards,
Rene.
-
Good Morning,
I have a problem when a call comes in through an agent group.
The caller-id is showing the connected phone number, it should present the name entered in the address book.
When I redirect this incoming call directly to an extension then the caller-id is replaced by the address book entry, it is displaying the configured name instead of the number.
Is this due to wrong configuring or is it an agent group related bug/problem?
Kind regards,
Rene
-
Ops, will be fixed in the next build.
Ok, if you have a new version please post the link for me so I can test it again.
Kind regards,
Rene.
-
Okay, that sounds reproducable. We'll track this topic and post when there is a fix available.
Thanks!
-
First, I would not use version 7.3.7. 7.1.35 is the best version for the pbxnsip right now.
Second, are you really using dialog state or are you using buttons? dialog state has many many problems and on snom phones buttons makes your life a lot easier.
Thanks for your reply.
I went already back to version 7.1.35 because 7.3.7 is spontaneously rebooting etc.
But also 7.1.35 gives this strange BLF behavior.
I have configured the buttons with PnP thru pbxnsip using the predefined “Busy Lamp Field (BLF)” option.
When an external call is connected and you want to transfer this to another internal extension with announcement, you place the external call on hold and push the internal BLF button for the internal extension. Then you can announce the external call and when it is ok to transfer you push the transfer button on the snom phone and press “V” to transfer. Then the BLF lamp from the internal extension remains blinking like it is on hold. Also the PAC is showing that the extension is on hold, but the extension is talking then to the external caller !
Kind regards,
Rene.
-
The latest and greatest currently is http://pbxnsip.com/protect/pbxctrl-3.1.0.3039.exe; not released yet but you'll see the progress!
Thanks, I have just installed this version.
I have found the setting in the webinterface. It seems exactly what I need but it looks like it is not working.
I have configured it to "1" so at least one agent should remain logged in, but they are all still able to logout.
And there is a problem with the codec configuration field, it is changed to a table with up and down buttons, but the configured codecs are not listed anymore, the table is empty. I have tested this with IE7 and with Firefox with the same results. I see the following error in the logfile, perhaps that is the problem:
Web Server: File codec_selection.js not found
Kind regards and keep up the good work !!
Rene.
-
Yes, that will be in 3.1. If you want a preview, let us know what OS you have.
Wow, that would be very nice, I am using the Win32 version.
Is there also something changed for the strange BLF behavior as I described in http://forum.pbxnsip.com/index.php?showtopic=1492 ?
Kind regards,
Rene.
-
Is it possible to create that feature "Have at least xxx agents in the queue"?
We already had some filled queue's without any logged in agents....looks not very professional to our customers!
Kind regards,
Rene.
-
Are there others who have seen the above problem?
Is there a solution for it?
Kind regards,
Rene.
-
Hi,
Is it possible to cut off some numbers from a dialed phone number?
Within the Netherlands we have 0900 pay numbers followed by 4, 6 or 7 other numbers. But sometimes you see numbers on a website (like Toshiba support: 0900-10001000) with too many numbers. The Dutch telecom provider KPN is not doing anything with that last number but my sip provider does. So if a 0900 number is longer than 11 digits then the last rubbish should be cut off.
I can think of a pattern “0900xxxxxxxx” but what would be the replacement?
Kind regards,
Rene.
-
I agree with that, hot desking will do the job.
It would be very nice if it could be possible to activate the hot desking feature from another extension.
So then I can program a button on the snom 320 for hot deksing that extension to the dect phone.
"Have at least xxx agents in the queue" would be also a perfect solution for preventing a queue full of callers without any agents!
Kind regards,
Rene.
Is it possible to create that feature "Have at least xxx agents in the queue"?
We already had some filled queue's without any logged in agents....looks not very professional to our customers!
Kind regards,
Rene.
-
We are experiencing strange BLF behavior on Snom 320 phones (firmware 7.3.7) with PBXNSIP 3.0.1.3023.
When an external call comes in through an agent-group and the secretary answers it she presses the button of the phone where to it should be transferred and announces the call.
The external call is put on hold automatically.
When it is okay to transfer she presses the transfer button (now the internal phone is also on hold) and then confirms the transfer with the “V” button.
Now the external call is transferred to the internal phone but the BLF of the internal phone keeps the status “hold” (slow blinking) while the conversation is going on. This is strange because it looks like the call is still on hold….
Could this be a bug?
Kind regards,
Rene.
-
Should be available now.
I have found the version 3.0.1.3023 and tested the pickup group settings; it is working great for us.
Thanks.
Kind regards,
Rene.
Version 4 RC
in Announcements
Posted
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.
Does anyone know how to handle these problems?
Kind regards,
Rene.