koolandrew

i was just wondering if Grandstream was set up the same way, as i have been told that Yealink LDAP does work on newer phones but the Grandstream does not. Is there a Grandstream favourite.xml file like with the Yealink phones. Thanks

No, sorry. It is an old version...does this only work on v 62?

Remember I said earlier there was no logs?

Ok. I don't see any evidence of such. I don't see any entire in the phone nor do I see any evidence if it in the web interface. what do you suggest?

I looked through the yealink_common.txt file again, and i dont see any reference to yealink_favorite.xml file, so i am stumped at this point. Please advise.

i dont really know, as it says that the the pnp file is limited to 2k, so i have really no idea as there are no logs after a certain point. I have the same issue for dial now and logo/wallpaper. Any suggestions, as the phone book is empty.

Thanks again for the quick reply, but it is woefully short of details. There are no phonebook entries now in a Yealink or Grandstream phone I have looked at the LDAP setting on a actual Yealink phone, and it appears to be provisioned for LDAP and enabled; yet, there are no contacts in the directory. I have looked at the directory for Local, Remote and LDAP and there is nothing. Please advise.

Just to clarify, for phone, i mean Yealink or Grandstream, not cell phone. Thx

Hello, I have been searching for this question or info, but cannot seem to find it. Our customer would like to have all the domain contacts (ie John Smith ext. 222 etc) published to his phone. Is there a way that the phone could pick up this information from Vodia. Is the only way to do this, is to maintain an active list of extensions manually, and then load them into the phone book, and then format them again, and manually import them into each phone. Surely there must be a better way than what i have described. thanks

Ok, i think im starting to get it. I thought maybe there was a way of selecting a group of phones, that would have different provisioning parameters. Thanks again for your input!!

Thanks for the reply so quick. 1. Is the http url the domain or public ip address? 2. Is there a way of changing this and other settings to only specific phone ( or extensions) according to requirements of the locations in the domain. Thx

Thanks for quick reply and suggestion about upgrading, which needs to be done. Although i need to test caller id as i received other posts where people have concerns about this since the upgrade. In the mean time, this is what i did to change the file: #Configure the logo mode of the LCD screen; 0-Disabled (default), 1-System logo, 2-Custom logo; phone_setting.lcd_logo.mode = 2 #Configure wallpaper #http://192.168.1.100/wallpaper.jpg #wallpaper_upload.url = http://192.168.203.183/rest/domain/localhost/image/logo/480x272 wallpaper_upload.url = http://pbx-public-ip/Logos/t22p_logo.dob #wallpaper_upload.url = {https-url rest}/domain/{domain}/image/logo/480x272.jpg phone_setting.backgrounds = Config:480x272.jpg My questions remain, we have three phone models, old T22P and T28P, and a new T29G, which is colour. How do i set it up to load 3 different sizes and one with colour. Do i still need a .dob file, as per the Yealink website How do i set this up for some phones in the domain, as some phones will be loaded with these changes and some wont, according to their location preferences. I hope these questions arent rudimentary but we have always used our own system for provisioning but would like to start using Vodia. Thanks

Could someone help clarify how to provide different logos for different screen sizes as well as monochrome and colour for the different types of Yealink phones. Also it says in the Yealink doc that it has to be a .dob file, but it doesnt refer to it in the Vodia examples. Thanks

Could you please explain further by your comment above. Most phones have the ability to register to primary and second sip servers, so i am not sure if that what this question is regarding, as it is not clear by the question or the response. Can you expand upon this as it is a very important topic.

Thanks for the update. The regex update might be a bit over my head. I was able to get it to work without the ^. i wanted to the same thing for Carribbean countries using the NANPA dialling plan, (ie 1340xxxxxxx 1268xxxxxxx etc, but i cannot apply the same logic. Any ideas for that, as it is a little simpler as there are always 7 digits after the area code. I want to create a separate entry for those dial codes as i would like to treat them differently. Thanks for all the help.