ahennis@voicespring.net

I am trying to get a Snom M700 with M65 handsets to auto provision with Snom redirection server but it does not seem to be working. PBX is 5.4.1a and the M700 base and handset are running firmware 355. Is this working?

Probably could use a little better error checking so that entering something like 27/12 or $%^ or 44444 is flagged as an error.

mm/dd is the correct format. From the service flag page on the PBX. and at https://vodia.com/documentation/serviceflags

The info about being locked out was third hand info. Customer told my tech and my tech told me. The lockout would be useful. If I have it set to disconnect after X failed attempts and the if there are Y separate attempts it locks you out for a set number of minutes. Having the option to reset would be good too.

We have the system set "Max PIN failure attempts before PBX disconnects the call: 3". If the caller enters the PIN incorrectly 3 times the call is disconnected but the account is also locked for what appears to be 30 minutes. Is there any way to reset this lock?

For users that don't have extensions is it OK to just put the cell number in the various stages of the hunt group?

It would be useful to be able to group service flags and preform logical operations on the groups. (!SVGFLAG1 | SVCFLAG2 & (SVCFLAG3 | SVCFLAG4))

Are phone numbers permitted in Stage 1, 2 and 3 of a hunt group or are these fields limited to only extensions? Can I for example can I put my cell phone number in stage 1? The documentation does not specifically state that stage 1, 2 and 3 are limited to only extensions but the description is worded such that it would seem that the only valid entry in stage 1, 2 and 3 are extension numbers and not phone numbers. Perhaps the documentation can be updated to clarify this. We are running PBX version 5.4.0.

This can be done but it is not easy and very time consuming. You basically have to change the web pages by editing the templates. Honestly, Vodia needs a better more user friendly way to restrict that can be accessed.

I tried to implement the “Call cell phone when new message arrives” feature for one of my domains. The feature seems to be broken on the new PBX versions 5.4.0 and 5.4.1. We tried on a PBX running 5.4.0 and on a different PBX running 5.4.1 and it fails as follows. When you leave a VM the system calls the cell phone but hangs up after a few seconds of ringing. If you manage to answer your cell phone before the system hangs up the system prompts you that you have a VM but hangs up before you can listen to the VM. We tried this on a PBX running version 5.2.5 and it works correctly. Is anyone else having this issue?

Great! Would it be possible that have it default to whatever is set for the domain and have the ability to override it for an individual service flag?

Would it be possible to add time zones to service flags. I have customers with offices in multiple time zones. Currently we have to adjust the times in the service flag.

Here is the programming for buttons 19-24 on the GXP2160. It needs to be in the file grandstream-gxp2100.xml. <!-- Multipupose Key 19 --> <P1440>{grandstream-button-type 19}</P1440> <P1441>0</P1441> <P1442>{button-label 19}</P1442> <P1443>{button-param 19}</P1443> <!-- Multipupose Key 20 --> <P1444>{grandstream-button-type 20}</P1444> <P1445>0</P1445> <P1446>{button-label 20}</P1446> <P1447>{button-param 20}</P1447> <!-- Multipupose Key 21 --> <P1448>{grandstream-button-type 21}</P1448> <P1449>0</P1449> <P1450>{button-label 21}</P1450> <P1451>{button-param 21}</P1451> <!-- Multipupose Key 22 --> <P1452>{grandstream-button-type 22}</P1452> <P1453>0</P1453> <P1454>{button-label 22}</P1454> <P1455>{button-param 22}</P1455> <!-- Multipupose Key 23 --> <P1456>{grandstream-button-type 23}</P1456> <P1457>0</P1457> <P1458>{button-label 23}</P1458> <P1459>{button-param 23}</P1459> <!-- Multipupose Key 24 --> <P1460>{grandstream-button-type 24}</P1460> <P1461>0</P1461> <P1462>{button-label 24}</P1462> <P1463>{button-param 24}</P1463>

Can anyone provide more info on exactly what this change is

.

Figured it out. I was using global button profile that could be assigned to multiple phones and not an extension specific profile. I usually use a global profile because I like the ability to switch to a text-based editing window for buttons. The extension specific profile does not have the ability to switch to a text-based editing window for buttons. It would be nice to be able to switch to a text-based editing window for buttons for extension specific profiles. Perhaps this can be added in a future version. Is the requirement to use an extension specific profile vs. a global profile for the agent login/logout status indicator to function by design or is it a bug in the system?

I have since upgraded to Vodia PBX 5.4.0 and this is still not working. I even tried a Snom 760 as was used in the video. Still does not work. Any suggestions as how to troubleshoot this issue would be appreciated.

You might take a look at this thread in regards to provisioning the M325 http://forum.vodia.com/index.php/topic/8244-snom-m325/

That would be great. It would be nice if there were some detailed documentation on how to add new phone brands and models to an existing system.

Once you get this figured out will we need to upgrade the PBX to get this to work?

I am running the latest Vodia server version 5.4.0 and it does not have any templates for the M325. It does have the M700 templates.

No. Don't use hold. Press the park button(s) that you configure.

If you put the park buttons on all the phones other people will be able to see the parked calls.

I use mostly Snom phones and can program one or more buttons to monitor the parking spaces. I am not that familiar with programming Yealink phones but you might take a look at this http://forum.vodia.com/index.php/topic/7932-button-yealink/

Why not use call parking?