< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
Best regards, Byron Campen
I don't think this is necessarily a bug - outbound decorators are triggered whenever a message is sent out on the wire (that is not astack level transmission). 401/407's are not exactly re- transmissions, they are new transactions that are generated at the UserAgent layer. I do understand how it makes it difficult for the application to deal withthis situation when it wants to manipulate a message only once. Is there something you can check to see if you've already decorated the message before and if so avoid the subsequent decorations? Scott-----Original Message----- From: resiprocate-devel-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate- devel-bounces@xxxxxxxxxxxxxxx] On Behalf Of Neal Sidhwaney Sent: Friday, November 02, 2007 6:13 AM To: resiprocate-devel; niklas.enbom@xxxxxxxxxxxx Subject: [reSIProcate] outbound message decorators Hi I notice in DialogUsageManager line 796 the profile outbound message decorators are copied to the SipMessage outbound decorators. I amseeing that this causes the outbound message decorators to be executedmore than once if the message is retransmitted, i.e. in the case of a 407 or 401 unauthorized returned from the server, thus my VIA headers are being added many times depending on how many times the message is resent. Is this a bug? Thanks, Neal _______________________________________________ resiprocate-devel mailing list resiprocate-devel@xxxxxxxxxxxxxxx https://list.resiprocate.org/mailman/listinfo/resiprocate-devel_______________________________________________ resiprocate-devel mailing list resiprocate-devel@xxxxxxxxxxxxxxx https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
Attachment:
smime.p7s
Description: S/MIME cryptographic signature