Thanks to everyone that helped. Very much appreciated. 
If anyone would like them I've attached the schema files into their components 
the combined make up the H350 standard. Some of the video conferencing phones 
I'm working with have additional requirements such as the sAMAccountName plus 
others. It's been an interesting investigation.
Best wishes



-----Original Message-----
From: openldap-technical [mailto:[email protected]] On 
Behalf Of Quanah Gibson-Mount
Sent: 27 May 2015 17:40
To: Michael Ströder; [email protected]
Subject: Re: H350

--On Monday, May 25, 2015 5:46 PM +0200 Michael Ströder <[email protected]> 
wrote:

> Dieter Klünter wrote:
>> If you don't have the chance to download h.350 schema you may create 
>> it on your own, use rfc 3944 as base
>> https://tools.ietf.org/html/rfc3944
>
> See attached rfc3944.schema - please test.
>
> Is it worth to ship this with OpenLDAP source distribution?

File an ITS I guess?  Can review it there.

--Quanah


--

Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration

Turner & Townsend plc
Queen’s Award for Enterprise: International Trade 2014
Construction Consultant of the Year |  Building Awards 2014, 2013
Global Consultant of the Year | NCE/ACE Consultants of the Year 2013
Outstanding International Business  | British Expertise International Awards 
2013

For further information and registration details visit our website 
http://www.turnerandtownsend.com

This email and any attachments (“the email”) is confidential and may also be 
privileged, is subject to copyright and may be read, copied and used only by 
the intended recipient. The recipient is responsible for virus checking this 
email. If you are not the intended recipient please immediately notify us, 
delete and do not use, disclose, distribute, copy, print or rely on this email 
or any part of it. Turner & Townsend does not accept any liability for any loss 
or damage from your receipt or use of this email. 

Please consider the environment before printing this email.

Attachment: commObject.schema
Description: commObject.schema

Attachment: commURI.schema
Description: commURI.schema

Attachment: h235Identity.schema
Description: h235Identity.schema

Attachment: h323Identity.schema
Description: h323Identity.schema

Attachment: sipidentity.schema
Description: sipidentity.schema

Reply via email to