Martin Steinmann wrote: > Michael Picher wrote: > > > >Robert, > > > >This is exactly what I was looking for when feature request was made. > > > >Also, while it wasn't in the initial feature request, I think the > >option code is great to have in there for the roaming user > scenario. > >This feature will also have huge benefits in a testing/debugging > >scenario where the Admin may want to test calling from a > particular location. > > I can see the value of DTMF activated routing as a debugging > tool. We should make sure that the DTMF feature code can be > activated / deactivated from the admin UI.
If the admin does not want a given location to be accessible via 'location code' dialing, it can leave the optional 'location code' field blank for that location. > > How does this work with Caller ID? We can set caller ID by > user and by gateway. How does this work with calls that go > out a local gateway in a branch office? Wouldn't the roaming > user have to use a DTMF feature code to route the call > through his/her home gateway in order to get that local > Caller ID? In cases that is important, the DTMF feature code > would have to be used in order to override the auto-detected > current location. Scott is in the middle or rethinking the whole caller-id strategy but my understanding of the current scheme is that the user can have a caller id and so can the gateway. When a user makes a call using a gateway then the caller-id of the user, if provisioned, takes precedence over the gateway-based one. I wasn't planning to add any additional caller-id-related logic for this feature. What I am proposing is a modification on how the gateways get selected but once selected the caller-id will be applied as before. But back to your real question which is (and I paraphrase): "If a roaming user needs to present his 'home base' caller-ID when making PSTN calls, how can we accommodate that in the proposed feature?". If that is truly important, this can be achieved in many ways: - Configure a user-based Caller-ID for the roaming user. That caller-ID will always be applied no matter which gateway gets used. - Do not configure any 'network topology' information for the locations. This disables the automatic detection of a user's location so that calls will always be made using the 'home-base' gateways. - If automatic detection of the user's location is required and must be enabled then its logic can be overridden by dialing with a pre-pended location code of the home base. > > The auto-detection of the current location of a roaming user > is very powerful. > > Location: In sipXconfig we are assigning a location to a user > and not to a phone, correct? The phone then takes the > location of the user assigned to it. In addition, we assign a > location to a gateway. Would like to make sure I understand > this correctly. That is all correct. Because we do not have GRUU we cannot reliably determine which phone instance we are talking to and therefore cannot determine its location. There is therefore no point in assigning location information to phones. There is one caveat which I'm sure you got but just for completeness, let me mention it here. When you say: "The phone then takes the location of the user assigned to it. ". That will be true unless the administrator has provided network topology information for the 'locations' it configured. If that is the case, the feature will first try to determine the phone's location based on IP addresses (to cover roaming users) and then fallback to the location assigned to the user if no match is found. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
