Jump to content


Member Since 22 Nov 2014
Offline Last Active Aug 03 2017 07:32 AM

Posts I've Made

In Topic: Service flags on Grandstream gxp2160

16 June 2017 - 01:32 PM

Looks like I was provisioning incorrectly. Setting up the service as a BLF works.

In Topic: Trunk Custom Headers

15 June 2017 - 08:01 AM

Wow. That was fast. Thank you.

In Topic: Service flags on Grandstream gxp2160

14 June 2017 - 09:34 PM

I am probably programming the Grandstream incorrectly since I do not have a lot of experience with the gxp2160. I tried setting it to a BLF in the button profile of the extension but it did not seem to work. I did not log into the phone to check if the button was actually programmed correctly. We started testing the Grandstream phones months ago but stopped because BLF did not work well. There have been many firmware upgrades for the Grandstream phones over the past 6 months. Now the BLF and PARK seem to work correctly. BLF and PARK are very important so it is good to see those features working reliable. Service flags are important as well so it would be good to see them working too, 


We mostly deploy Snom phones so we are spoiled in that we can just program things and they work. However the Snom phones look a little dated. The gxp2160 looks great and are at a nice price point. It would be nice if the Grandstrem phones could work as easily as the Snom phones. Since V-tech purchased Snom we could possibly see some more up to date models from Snom/V-Tech. 

In Topic: Trunk Custom Headers

14 June 2017 - 09:21 PM

This is really great news!!! Thank you for considering my request and implementing it so quickly.


So is it possible we could see this in v58 or 59? My background is in programming so I understand that features can be delayed due to unforeseen factors.

In Topic: Trunk Custom Headers

14 June 2017 - 06:09 PM

Yes domain-paramX also makes sense!

This is great to have the variables exposed. 


Will we also be able to do logical tests on the variables so we can change the header accordingly? For example using {if clip true} checks if the variable clip is true allowing us to return a different value if variable clip is set to true or false. Maybe something like {if ext-param1 isblank} or would it be as simple as {if ext-param1 ""} to make a string comparison with "" meaning a null value. I prefer the later as it is more flexible and allows not only checking if a variable is null but also if it is equal to a value. 


For example in the below statement we are checking if the ext-param1 field has been populated for an extension making a call. If the variable has a non blank value the system would return {ext-parm1} else it would return {domain-display}.


{if ext-param1 isblank}"{domain-display}""{ext-param1}" <sip:{if clip true}anonymous@anonymous.invalid{fi clip true}{if disa true}{ext-ani}@{domain}{fi disa true}{from-ani}@{domain}>