[Serusers] Associating a contact address with a location

Hi, Sorry to resubmit on much the same topic as before (Portal for forking call to preferred end device-sequential ringing) but I was wondering if anyone had any further ideas on how to associate a particular contact address with a location. i.e. a user can choose that their preferred location is their desktop phone and I need to devise some way to know that a particular contact address is associated with the desktop phone. I was thinking the user must either enter the device ip addresses manually so I can search the contact based on IP address (This sucks in terms of NAT, scalability and losing mobility over networks) OR I could perhaps stipulate that a user cannot have two of the same device e.g. cant have two BT100 hardphones and I could search the location table based on model. I think either of these options aren't great....Which is why I was wondering if anyone had any better ideas? Many Thanks, Aisling. p.s. I currently retrieve the users contact address and q value via a web interface using the serctl fifo interface. -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: 22 June 2005 12:45 To: Aisling Cc: 'Greger V. Teigre'; jh(a)tutpro.com Subject: Re: [Serusers]CPL - Portal for forking call to preferredenddevice-sequential ringing Hi Aisling, There are many ways to implement serial forking - like using CPL, LCR or AVPOPS. But the main idea (if I getting right from your initial email) is to allow the user to order his contacts for the same account (like account userx that have contact_pda_x, contact_PC_x, contact_office_x, etc). So you have all this contacts in user location, you have several mechanism for serial forking, but you are missing the link - to get the contacts from user location and to feed any of the serial forking mechanism. This is the big problem. even if you use CPL, you need to place in each location node the contacts (and not the AOR) of the user, contacts which are dynamically stored only in user location. what you are describing below can be possible only if you a user (as person) has different sip accounts (SIP users) for each of his devices. Other way I don't see how you can place in the CPL script the "phone1" and "phone2" addresses. and just to answer you to the CPL- related questions (from implementation point of view): - each user can have only one script - if you load a new script, the previous one will be lost (overwritten). If you can different services via CPL (like screening and no-answer), you need to mix them in the same script during provisioning. - if you want to delete a CPL script via FIFO, use the REMOVE_CPL command: serctl fifo REMOVE_CPL user@domain regards, bogdan Aisling wrote: or be cpl -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.