Well, I'm having a problem with the stack I'm using and I think that maybe it uses displayname for identifying the transaction. I just want to be sure if it is ok for the UAS to change the display name. I noticed the problem when testing a new UA that removes the displayname from the To header. I think I will solve it by removing the displayname from the To header since that give no extra functionality... the risk is that if some other UA adds a displayname maybe that I can't identify that transaction instead.
The first thing I would like to to is to find out which behvaior is correct, to change or remove the displayname or leave it as it was in the incoming message Regards, Andreas -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Hans Persson Sent: den 16 december 2003 11:20 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] To field in responses m�n 2003-12-15 klockan 09.59 skrev [EMAIL PROTECTED]: > > I'm reading RFC 3261 and have a a question of how responses are > > created. > > > > In 8.2.6.2 I can read that if no tag in the To field is recevied, > > the URI of the To in the response MUST be equal to the To URI in the > > request (and a To tag is added). As I understand, the display name > > is not part of the URI, does this means that the Display name can be > > different in the request and the response? can I even remove the > > display name when creating the To field for the response? > > Display Name is optional in URI. so it does not matter if display > name is there or not or is different. u compare only URIs. But that only applies to a To header without a tag, as far as I can see. For a To header with a tag (or a From header), the header field must be equal, not just the URI, and that would mean that the display name can't be changed in those cases. Why would there be a difference in whether display-name can be changed? Hans -- Hans Persson <[EMAIL PROTECTED]> Ingate - Firewalls with SIP & NAT Ingate Systems AB +46 13 210857 http://www.ingate.com/ Private: <[EMAIL PROTECTED]> http://www.lysator.liu.se/~unicorn/ _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
