Bugs item #1524046, was opened at 2006-07-17 14:49 Message generated for change (Comment added) made by di-shi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1524046&group_id=139143
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Di-Shi Sun (di-shi) Assigned to: Di-Shi Sun (di-shi) Summary: OSP module sends OSP token to non-OSP device Initial Comment: OSP module inserts OSP authorization tokens in the SIP INVITE messages sent to non-OSP devices (OSP server returns 0.0.0 as the OSP version of these devices in OSP AuthorizationResponse messages). If there are multiple routes in an OSP AuthorizationResponse message, the OSP authorization token of the first route is used for all routes. The correct action is to use route specific OSP information for different routes. If the destination is not an OSP device, no OSP authorization token is sent in the SIP INVITE message. ---------------------------------------------------------------------- >Comment By: Di-Shi Sun (di-shi) Date: 2006-07-17 15:10 Message: Logged In: YES user_id=1470964 This bug has been fixed using branch route approach. The changes are committed into CVS head on 7/17/06. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1524046&group_id=139143 _______________________________________________ Devel mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/devel
