On Wed, 2008-07-09 at 10:28 +0100, Gabor Paller wrote: > It seems that the registrar uses the From (or To) header to extract the > principal and then it does not cut the port part. Therefore the GJTAPI > registration request is rejected. > > Whose fault is it? It seems illogical for me to use the From/To header > for identifying the principal when there is the "username" field in the > Authorization header. On the other hand, the user name in the From field > does seem unusual.
The use of these values is not perfectly standardized. In sipX, the "user" who possesses credentials is assembled from a user-name, a host-name, and optionally a port: "[EMAIL PROTECTED]:port". You can see the valid credentials in the file /var/sipxdata/sipdb/credentials.xml. In the Authorization header, only the user part is used (IIRC), but the full URI is the address which that user is allowed to register for. Now in your case, it looks like your UA is trying to register against <sip:[EMAIL PROTECTED]:5064> (the To URI), but it's likely that for one reason or another, the URI in the credentials file is <sip:[EMAIL PROTECTED]>, which is not the same. You've got to have sipX and the UAs agreeing on the host-port of the URIs in your SIP domain. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
