You are here

Grandstream Zero Configure over MESH Issues

3 posts / 0 new
Last post
WD6EBY
Grandstream Zero Configure over MESH Issues
Hello All,
I have a UCM1602 and am using the GXP1625 as the principal telephones for this Ventura County MESH telephone project.
I can configure the phone with the Zero Config option only when I the telephone is connected directly to the UCM as it should.  I can make and receive calls, I can download XML display screens and the LDAP directory works as it should.  However when I connect the phone to the UCM through the MESH, I loose the ability to do a Zero Config, I have no LDAP, but I can still do a XML display update.  I have not yet discovered if I can do a phone revision upgrade through the MESH. That's a TBD.

I believe the issue might be with the limited subnet that each node is relegated to.  I think if I could set my local NODE's LAN Subnet Mask to 255.0.0.0 instead of the default 255.255.255.240, these "over the MESH lost features' might be available.

If anyone has any suggestions or has had the Grandstream system work as it should through the MESH I would like to hear from you.  I like the concept of having a central management and being able to push updates and changes to the phones takes the burden from the individual and provides for everyone having the same instrument configuration.

Thank you for your help.

Respectfully,
Paul, WD6EBY
WD6EBY
Hello All,
Hello All,
 
I have a understanding to my above issues.  As it turns the Grandstream UCM1602 cannot fully recognize or communicate with the MESH telephones because the UCM cannot Span Subnets.  My NODE is setup as 13 Host Direct, DHCP enabled with an address of 10.109.26.81, the PBX did pickup 10.109.26.82 and all seemed fine.  As it turns out when I ran the ZeroConfig feature it was looking for address from .81 down to .20 which missed my MESH hardwired phones with a NODE DHCP assigned address between .81 to .94.  We shelled into the NODE and changed the Subnet address from 255.255.255.240 to 255.255.255.0.  This allowed the ZeroConfirure on the PBX to see the whole Subnet address group and properly recognize and configure the phones.
 
I did see that the GUI still showed the Subnet as 255.255.255.240.  I suspect if I were to refresh the GUI my command line change would revert to the GUI entry.
 
So let’s take this experiment to the next step and change the Subnet address to 255.0.0.0.  In my mind this should not encumber the ZeroConfig function due to its Subnet Spanning Issue.  I can report that we had issues.  First off we lost contact with the NODE over the DTD link but still hade local GUI and Command line access.  We were able to change the Subnet back to 255.255.255.0 so I did not have to reset the NODE. 
 
So my big question, why there was there an issue when I changed the Subnet to 255.0.0.0.  If I could use this full Subnet, I believe this would provide full control of the phones over the MESH network.  Any help or suggestions would be welcomed.
 
Thank you
Paul
WD6EBY
 
KG6JEI
"So my big question, why
"So my big question, why there was there an issue when I changed the Subnet to 255.0.0.0.  If I could use this full Subnet, I believe this would provide full control of the phones over the MESH network.  Any help or suggestions would be welcomed.
 "

Modifying the system configurations at this level is a V3 protocol violation and is not expected to work.

Regarding the UCM: I don't know it off hand but odds are it actually functions on A broadcast domain which will never transfer the mesh. broadcasts can not pass through routers (which essentially every mesh node is acting as a router). A broadcast is the only way it could be a true "zero" configuration, most phone system support setting up a configuration server manually however, might be something to look into.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer