On Wed, Aug 20, 2008 at 3:27 PM, Dale Worley <[EMAIL PROTECTED]> wrote: > On Wed, 2008-08-20 at 14:56 -0400, M. Ranganathan wrote: >> No telling what ITSPs will ask you to put there :-) But there is >> another reason. Sometimes, ITSPs want you to put a specific user part >> whereas the address in the From is your global address which you might >> not know a-priori especially if you are using dhcp. Splitting things >> in this fashion allows one to specify parts of the URL that one wants >> replaced as the request is forwarded. > > There are two different questions here -- one is how caller aliases > work, the other is how the user enters caller aliases. > > In regard to how caller aliases work, the current scheme (as far as I > know) is that the configuration database contains the replacement URI, > it *never* incorporates parts of the original From URI or other dynamic > information. If we need to generate a From URI that is > "sip:[EMAIL PROTECTED]", we will need to > expand the caller-alias mechanism. > > In regard to how users enter caller aliases, we should be thinking about > what users want to do, and different users might want to do different > things. E.g., it might be useful to provide one field for entering the > alias as a full URI and a second field for entering just a user-part. > When the second field is "done", the UI would combine it with the proper > other elements to form a full SIP URI and write that result into the > first field. That combination allows users to enter full URIs, but also > makes it easy to do the usual task, which is to just provide alternative > user-parts.
Sounds good but one problem. RIght now there is no global address discovery service (should we have one?) hence if the user calls for sip:[EMAIL PROTECTED] how is sipxconfig going to discover what that global IP address is? Perhaps sipxconfig should include a stun client for dynamic address discovery as this information is required in a couple of different places (sipxbridge and far end NAT traversal) or perhaps sipxconfig can have a system page where one enters the global IP address. Finally there is the case where the registration authentication user name and ITSP proxy domain should be used as the caller ID . This, information only sipxbridge knows at the moment. I have a switch for that as I was unable to enter a full sip URL in the past. I think I can get rid of this switch if the user is able to enter the entire sip URL in the caller ID field. Regards Ranga. > > Dale > > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
