Thanks for the approach! I had considered a variation of this (making a workstation a "user"), but I was a little concerned about having to account for them wherever "real" users are referenced. For example, in a report that lists data on all "users" I would not want to include users that are actually just workstations.
This is definitely on my list of options. Does anyone happen to know of some field that can be used to mark a user as "different" from real users? The "hoteling" feature however, looks like it might be spot on, even seems to include aastra phones. I have some investigating to do ^_^ Thanks again! From: [email protected] [mailto:[email protected]] On Behalf Of Nathaniel Watkins Sent: Thursday, April 12, 2012 11:37 AM To: sipXecs developer discussions Subject: Re: [sipx-dev] Associating a phone to a workstation instead ofa user You could do the following: 1) Setup your actual user as a 'phantom user' - do NOT assign a phone (you 'may' want to use the username as the ext, so it can match the logged in user on the computer network) 2) Setup your 'workstation phones' as users (user & phone) with an extension (ext. 2001, 2002, etc) - this user would be named workstation 1,2,3,etc. 3) Develop a small program or web page that would modify call forwarding for the actual user in question via soap/rest apis (depending on the phone, and number of users, it could be written to work with the microbrowser on the polycom phones). 4) On logon, the app would modify call forwarding for the 'phantom user' and route calls to the workstation phone number. The softphone option would obviously be much easier... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: Thursday, April 12, 2012 11:32 AM To: sipXecs developer discussions Subject: Re: [sipx-dev] Associating a phone to a workstation instead of a user On Thu, Apr 12, 2012 at 11:06 AM, Dan Chang <[email protected] <mailto:[email protected]> > wrote: > I am trying to "associate" a phone with a workstation so that , when a > User logs in to a particular machine calls to the user are routed to > the phone associated with that machine. My understanding of how > SipXecs handles provisioning now is that a phone is directly associated with a User. Sounds like "hoteling" you familiar with that? http://track.sipfoundry.org/browse/XX-9864 <http://track.sipfoundry.org/browse/XX-9864> What brand is the phone? If it's a soft phone, it can be programmed to automatically register/unregister as you desire. No need to create a "phone" object. _______________________________________________ sipx-dev mailing list [email protected] <mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ <http://list.sipfoundry.org/archive/sipx-dev/> ________________________________ This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Garrett County Government, 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.org
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
