Hey BJ, Its all about IP. Basically the softphone has a config button where you can specify your 'source' ip in a drop down of bound addresses. I usually just make sure the IP associated with the RAS connection is selected (purely for the audio stream), then the IP phone will register with CM (because it is programmed with the IP of CM), and CM will recognize and record the source ip of the phone.
When CM sets up a call between two endpoints, it notifies each of the phones of the other's IP, handles the codec negotiation, etc, then steps out of the conversation and the two endpoint's RTP streams go direct. Now, if you're referring to Locations as they relate to CM, and not physical Locations, that's a different ball game. Locations in CM are used for CAC (call admission control) to limit how much bandwidth is used on the wan between sites or internal on the lan for a site (unfortunately there's no distinction between them). Personally, I haven't used this in production yet. What little I've played with it in the lab, I really didn't like the implementation in CM. I think they've got a little ways to go before this will be solid. Just my opinion, of course. Hope this helps, Vance ""B.J. Wilson"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Hi Vance - > > I too am studying All Things VoIP, and I'm curious how this would work. > Say you have User A trying to call User B. User B is currently in the > office. So User A dials '1111' which is User B's phone number (or "route > pattern" if you want to be specific). CallManager picks up the route > pattern, looks up User B's location, and forwards the call on. All is good. > Now, say User B is telecommuting. How does CallManager know this? How > does your RAS (remote access) server notify CM that User B's geographical > location has moved? Is there something in User B's RAS (Registration, > Admission and Status) setup that alerts CM to the fact that they're dialing > in from home? > > Thanks, > > BJ > > ----- Original Message ----- > From: "Vance Krier" > To: > Sent: Wednesday, October 16, 2002 4:08 AM > Subject: Re: VoIP Clarification. [7:55682] > > > > Hey Stu, > > > > In simple terms, yes you are correct. However, as I'm sure you know, you > > need to take this type of setup with a grain of salt. If you have a > decent > > bandwidth, low latency, consistent connection between the phone and CM, it > > works fine. There's absolutely no guarantees for QoS on the Internet. > > Now, FWIW, I use softphone on my laptop when I travel and I've gotten > > satisfactory results (IMO) better than 75% of the time. > > > > I always pitch this as being a *kewl* feature, but never as a selling > point. > > I'm > > very, very cautious with customers over this. As long as the user > > using it is understanding and realizes there will be times when it doesn't > > work or the quality is really crappy, then typically they stay happy. Not > > something I'd give to Internet/computer/technology illiterate executive. > > > > I love it, by the way. > > > > Good luck, > > Vance > > > > > > > > ""Stuart Pittwood"" wrote in message > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > Good Morning all, > > > > > > I am just starting to look into VoIP as I have been asked by my manager > to > > > do some research and find out if there are any benifits from VoIP for > our > > > firm. > > > > > > Am I right in saying that if we had a solution based on Cat 6000 (or > > > similar) switches, with a cisco VPN solution for the home workers, that > > > users who use their laptop at home with cisco softphone or hardware > phone > > > could have their telephone extenstion follow them? > > > > > > Please forgive the simplicity of my question, just making sure I am > > thinking > > > along the right lines. > > > > > > Thanks > > > > > > Stu Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55713&t=55682 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
