Search the Community
Showing results for tags 'grandstream'.
Found 3 results
I just installed last versione of vodia (63.0.2) and some gxp1610/15 grandstream phones (fw 126.96.36.199 and 188.8.131.52). When I click on LDAP search softkey button and I search for like letter "A", phone freezes and I've to reboot disconnecting the power. Someone can reproduce this issue with a grandstream phone? Thank you. Not sure is a bug on gxp fw or other thing. Regards, Alessandro Marzini
Hello, Just got Vodia iop and am working to set it up. Using the built in license. Created domain, extensions, and was able to bind the phone's mac to an extension. I opened the account for MAC based provisioning, rebooted the phone, factory reset the phone, and it will not provision. No buttons light up and the phone says not configured. I also tried changing the provision url, because whenever I factory reset, it goes to a 3CX url. I can't remember if that's normal or if it's because it was used for 3cx I updated the firmware on the phone to the latest Version 184.108.40.206 IOP is on Version: 61.1 I followed directions here: https://doc.vodia.com/pnp_prerequisite_steps https://doc.vodia.com/pnp_grandstream
I recently added a Grandstream ATA (firmware v220.127.116.11 [latest]) to my snom ONE PBX (5.1.1 (Win64)). Caller ID works fine with the Grandstream ATA (i.e. the attached phone displays the CID) if the Trunk Routing/Redirection Default Account is set to the ATA's assigned extension. However, if the ATA extension is part of a Hunt Group where the Behaviour: From-Header is set to Calling-Party (or any other setting), the ATA's attached phone simply displays "Incoming Call". I don't have any experience debugging these kinds of problems and any help would be appreciated.