Firmware for UCM6202/6204/6208/6510 released as Beta



I’m not sure what you mean. This basically just allows you to add a custom device model, create templates based on the original device, and assign it to devices found via ZC.


@GS.Jimmy, are you saying I can take any IP phone, say a Yeastar IP phone, and now configure it via Zero Config?


Only if the phone supports the p-values and available options of the template that it is assigned. If a Yeastar IP phone somehow has the exact same configuration values as the selected model, then it might work.


and this thing you can not already do it by creating a custom model?


With this version, I can not use a phone call to the GS Wave web client anymore in the Google Chrome browser on Mac OSX. Video works (tested in same network).


@drostoker @damiano70
Let me explain: Grandstream can make OEM and modified version for big sales They are not really original one so they are not correctly recognized by UCM. This feature allow add them to provision in UCM.

No yealink or other as provision templates will be wrong (gs format with yealink values).


so far it was clear to me, as it is interesting I would like to know how to do it (for example on a Snom 300)


You cannot, this is only for GS OEM units that share same provision as normal SG phones (they have different model name (little).

Only way to “provision” other brand is keeping file in USB/SD and allow them to configure from there(via ready file). It is just way to keep files in uCM and nothing to do with ZeroConfig GS phones provision.


I still do not understand what it is used for and how it is used, I gave the example of Snom because you have given the example of Yealink. When the new UCM manual comes out, I hope it will be written down what it is used for and how it is used.


You NEED to have custom grandstream phone to use it, this is only option for them.


ok @Marcin , this is the only thing I think I understand :grinning:


That’s strange. I am unable to reproduce the issue you’re encountering on my end. After prepending 9 to the default “${CALLERID(num)}”, I can see it on the CID info of calls using that inbound route. Perhaps you can file a ticket on the issue with configuration details, traces and syslogs?


Thank you for the feedback. Please file a ticket regarding this issue with a log of the call. You can get start a log through the GS Wave web client in the top right corner.


Thank you for your answer. I just wants to clarify, so you are see “9” ahead CID on a screen of your phone during you have incoming call? Right? Or in a record somewhere?


Thank you for your answer. I just wants to clarify, so you are see “9” ahead CID on a screen of your phone during you have incoming call? Right? Or in a record somewhere?


You will be able to see it on the phone screen.


Thank you. Unfortunately I don’t have it, I think some settings can make a restriction for this, but I have been check all of it, trunk, extension, inbound rules… and nothing


In fact, everything I do doesn’t any sense, the phone screen shows only the number of the incoming subscriber. :frowning:


When is directory support going to be ready? I installed this yesterday only because I read something about better LDAP in the .18. version, without much further explanation. Then got the .19. minutes later because of the same reason. I’ve been waiting for directory integration since my first unit several years ago.

Instead, I found yet another feature without central userbase and the LDAP support only for contacts/address book and Wave Web…which is not going to be used anytime soon without a central userbase.

Still, I tried to make the best out of it and at least use the LDAP contacts feature, thinking hopefully I can manage to hack it once it syncs with the PBX but that’s not an option as it doesn’t allow spaces in the username box, it demands for a distinguished name. THOSE MOST OF THE TIMES COME WITH SPACES IN THEM. I couldn’t find anything in my directory without a space in the DN. UPN-style usernames are not allowed.

I have 7 extensions, at the most 9, only, part of it is that nobody wants to have another account but besides that, my unit already feels sluggish and with more stuff piling on it by the time directory integration comes–if ever–it’s going to be unusable.

The password is still complexity-limited, a rather big security flaw these day; I actually issued a ticket about this and that annoyingly got routed again to Grandstream Latin America where I emailed back and forth for over two months with whom had clearly no idea what I was talking about for the duration of this period and got me nowhere. I wasn’t even asking for anybody to solve my problems, just some sort of guidance/documentation so I could go into the CLI and Kerberize my device or something.

Kudos to you for keep adding features and not nickel-n-diming customers, but please focus on the what’s important first. Directory integration is crucial, or at least federation (like SAML, OpenID Connect…) if you want to keep the web direction you got going on lately.


Looks like you might have to file a ticket with traces and syslog.

Thank you for the feedback! The issue has been confirmed and reported.

Thank you for the feedback, and I apologize for your poor experience with support. Would you happen to have a ticket detailing the feature request for directory support? I would like to reference it when bringing it up internally. Additionally, the password limitation issue will be reported.