Hi all,
What attribute are you using to represent an internal telephone extension?
Can't see any standards based ones.
Thanks.
Gavin Henry ghenry@suretec.co.uk wrote:
What attribute are you using to represent an internal telephone extension?
Our site just uses telephoneNumber with the full number, and leaves it to the users to know when they can skip the initial part.
Hallvard
On 10 August 2012 15:48, Hallvard Breien Furuseth h.b.furuseth@usit.uio.no wrote:
Gavin Henry ghenry@suretec.co.uk wrote:
What attribute are you using to represent an internal telephone extension?
Our site just uses telephoneNumber with the full number, and leaves it to the users to know when they can skip the initial part.
OK, thanks!
Le 30/07/2012 21:46, Gavin Henry a écrit :
Hi all,
What attribute are you using to represent an internal telephone extension?
As telephoneNumber was already used, I used another attribute (homePhone) and a view to present to our cisco call manager using the expected name (telephoneNumber):
moduleload back_relay.la
# virtual context for the call manager database relay suffix ou=telephony,dc=domain,dc=tld overlay rwm rwm-suffixmassage ou=users,dc=domain,dc=tld rwm-map attribute telephoneNumber homePhone rwm-map attribute telephoneNumber rwm-map attribute *
Hi all,
What attribute are you using to represent an internal telephone extension?
As telephoneNumber was already used, I used another attribute (homePhone) and a view to present to our cisco call manager using the expected name (telephoneNumber):
moduleload back_relay.la
# virtual context for the call manager database relay suffix ou=telephony,dc=domain,dc=tld overlay rwm rwm-suffixmassage ou=users,dc=domain,dc=tld rwm-map attribute telephoneNumber homePhone rwm-map attribute telephoneNumber rwm-map attribute *
Sneeky! something like telephoneExtNumber would be perfect.
openldap-technical@openldap.org
-
Gavin Henry -
Gavin Henry -
Guillaume Rousse -
Hallvard Breien Furuseth