Adding phone templates

[RichardDCG]

Is there a way to add phone templates (not modify).  The GS GRP2634 is not available on any version PBX yet, is it something we can add ourselves?

[Vodia PBX]

Yes its possible, but not easy. You need to change the pop_grandstream.xml file and then add a new entry for the new file. The new file must be in the file system because there is to existing file built-in. If you put the pnp_grandsteam.xml into the file system as well you'll need to restart the service to have the PBX pick up file changes.

[RichardDCG]

Thanks.  In looking at this file I can see:

  <file name="grandstream-grp261x.xml" encoding="xml">
    <pattern mac="3">cfg############.xml</pattern>
    <user-agent>Grandstream.*GRP26..</user-agent>
    <prefix>true</prefix>
    <vendor>Grandstream</vendor>
  </file>

I assume then that the GRP2634 would be included under the user agent Grandstream.*GRP26.. ?  And I should only modify the GRP261x.XML file?

 

If, for arguments sake, I wanted a specific one for GRP2634 I could add:

  <file name="grandstream-grp263x.xml" encoding="xml">
    <pattern mac="3">cfg############.xml</pattern>
    <user-agent>Grandstream.*GRP263.</user-agent>
    <prefix>true</prefix>
    <vendor>Grandstream</vendor>
  </file>

 

and then need to modify (so the user agent would not get confused?):

  <file name="grandstream-grp261x.xml" encoding="xml">
    <pattern mac="3">cfg############.xml</pattern>
    <user-agent>Grandstream.*GRP261.</user-agent>
    <prefix>true</prefix>
    <vendor>Grandstream</vendor>
  </file>

[Vodia PBX]

Yes that looks okay. We still have the topic of the buttons which is another tricky area with the Grandstream phones (every model seems to have their own PXX values ) and for that we would have to change the models.js but lets do one step at a time...

[RichardDCG]

where do I place the new file? - grandstream-grp263x.xml

 

(will all my hard work then be overwritten with a new version?)

[Support]

17 hours ago, RichardDCG said:

where do I place the new file? - grandstream-grp263x.xml

You can simply add this section inside the file pnp_grandstream.xml and then save and reboot the PBX service as suggested earlier.

Also make sure that below setting is turned on. See image.

17 hours ago, RichardDCG said:

(will all my hard work then be overwritten with a new version?)

You have to take off (copy) all the customizations, backup the PBX directory, upgrade the PBX, and then put the files back in (in accordance with the how the PBX will accept those files) to keep the customizations from going away.

[RichardDCG]

I updated the pnp_Grandstream file with the below. This is for the Grandstream GRP2634 phones.

  <file name="grandstream-grp263x.xml" encoding="xml">
    <pattern mac="3">cfg############.xml</pattern>
    <user-agent>Grandstream.*GRP263.</user-agent>
    <prefix>true</prefix>
    <vendor>Grandstream</vendor>
  </file>

<file name="grandstream-grp261x.xml" encoding="xml">
    <pattern mac="3">cfg############.xml</pattern>
    <user-agent>Grandstream.*GRP261.</user-agent>
    <prefix>true</prefix>
    <vendor>Grandstream</vendor>
  </file>

 

I rebooted and the grp2613 is not there as an option.  The PBX is set to Read from file system. PBX is V68.0.2.

[Support]

Are the file grp2613 and grp263x different? Have you tried to provision the phone before making any changes?

Because it might work, with only a few changes needed?

 

[RichardDCG]

might have created some confusion.  I am trying to add a GRP2634 grandstream phone.  It does not accept any other GRP templates.  Are there plans to include these or a straight forward way to add templates as required?

 

When I add the MAC and provision it is detected as a GRP2634 when I look under 'Buttons' on the extension.

 

PBX 68.02 and test in 68.0.5.beta

[Vodia PBX]

The GRP2624 and GRP2634 were not on the list. We don't have those models in our test lab, but thanks to the better aiming scheme they should work as well with the GRP template. The only question is if the number of VPK, MPK and EXT keys are correct. We assume the following:

GRP2624: { vpk: 32, mpk: 12, ext: 0 }
GRP2634: { vpk: 32, mpk: 10, ext: 160 }

Anyhow if you want to try please use the 68.0.5.beta.

[RichardDCG]

V68.0.6 notes state - Grandstream: Support for GRP2624 and GRP2634 models, but no template?

 

Nor is there one for the WP820 that has been out for a while.

[Vodia PBX]

The template is the same: grandstream-grp261x.xml. The pattern is Grandstream.*GRP26.. so this should work?

Hmm yes the WP810 and 820 are missing. It seems they did not make it into the release process yet.

[RichardDCG]

Thanks, can we rename the template - grandstream-grp26xx.xml ?  261x seems specific to the 261x series.

 

    {elif model == "grp2624"}
    <item name="provisioning.firmware.serverPath">{parameter grandstream-firmware-grp2624}</item>
    {elif model == "grp2634"}
    <item name="provisioning.firmware.serverPath">{parameter grandstream-firmware-grp2634}</item>
    {fi}

But nether is listed in the Phone parameters section?

[Vodia PBX]

16 hours ago, RichardDCG said:

Thanks, can we rename the template - grandstream-grp26xx.xml ?  261x seems specific to the 261x series.

Well at this point its just a name. Renaming would cause problems with upgrade, its better to keep the name even if it covers additional models. 

Please check if you have modified the pnp_grandstream.xml file. Here it shows that the parameters are in that file.

[RichardDCG]

I must have at some point modified the pnp_grandstream file.  I deleted that and now the phones are listed in the parameters section?  I didn't do any reboot or reset, the change seemed to be instant.

[Vodia PBX]

I guess that is how things should be!

[mskenderian]

I am glad I saw this, I was just told by support team that it is not possible to add our own templates.

any chance to add Grandstream GSC3510 / GSC3505.

[Vodia PBX]

Looks like a very cool device. I want a couple for home, so that I can page the kids when dinner is ready! Do you have a working config that we can use as base for the provisioning template (maybe attach that to a ticket)? I guess we need something for multicast and something else for unicast? 

[mskenderian]

Yes I attached it to my ticket about a week ago.

pretty much the same as any grandstream phone. Same p values. It also support xml version 2, which grandstream introduced a while ago, which doesn’t require p values, instead it uses the names from the web gui.

# SIP Server
P47 =

<!-- SIP Server -->
<item name="account.1.sip.server.1.address"></item>

I was thinking we can skip multicast and unicast if we can just assign the unit to an extension, and page the extension. By default it’s on auto answer.

the problem with *cast, we must know the clients network. To make a speed dial button on the phone to be able to send a *cast to all intercom units.

the other issues with just using *cast if client has multiple locations and they want to page another unit in another location. 

[Vodia PBX]

4 hours ago, mskenderian said:

Yes I attached it to my ticket about a week ago. 

Hmm nothing in the ticket system that would match GSC3510. Can you try to open a new one? It would be great if we can use "real" names, those P-values are very hard to read for humans.

[mskenderian]

8 minutes ago, Vodia PBX said:

Hmm nothing in the ticket system that would match GSC3510. Can you try to open a new one? It would be great if we can use "real" names, those P-values are very hard to read for humans.

Ticket# 487882

[Vodia PBX]

11 minutes ago, mskenderian said:

Ticket# 487882

There is no ticket with that number... Are you sure this is on the Vodia ticket system

[mskenderian]

lol. no wonder all my tickets that i created emailing: support@vodia.com or creating a ticket via support.vodia.com, nevers gets answered.  

no its for sure its there, hamlet confirmed when i called.

 

 

[mskenderian]

11 minutes ago, Vodia PBX said:

There is no ticket with that number... Are you sure this is on the Vodia ticket system

sent you a PM with the full screenshot.

[Vodia support]

There is only 1 ticket open, for FAX. API. Not 100% if the tickets got merged somehow.  In anycase could you re-open the tickets you would like get resolved answered.   Orange means it's open, Green means it's closed.