[Serdev] [Tracker] Updated: (SER-208) Use of save_noreply() in reply_route block.
Jan Janak (JIRA)
tracker at iptel.org
Thu Jun 26 00:05:20 CEST 2008
[ http://tracker.iptel.org/browse/SER-208?page=all ]
Jan Janak updated SER-208:
--------------------------
Fix Version/s: Ipteldorf
(was: Wishlist)
> Use of save_noreply() in reply_route block.
> -------------------------------------------
>
> Key: SER-208
> URL: http://tracker.iptel.org/browse/SER-208
> Project: SER
> Issue Type: New Feature
> Components: Registrar
> Affects Versions: Ipteldorf
> Reporter: Atle Samuelsen
> Fix For: Ipteldorf
>
>
> Use of save_noreply() in reply_route block.
> It would be nice to have a feature where you could use save_noreply() in a reply_route block. This to update a local location database for users, so that a main proxy would not need to know the whole path out to a user.
> scenario:
> proxy A (main proxy) Proxy B (Edge proxy) UA
> <- REgister <-register <-register
> 401 -> ->401 ->401
> <-register w/challange <-register w/challange <-register w/challange
> ^Trigger onreply_route
> <200 OK -> 200 OK -> <-200 OK
> ^ Troggers save_noreply in onreply_route.
> - Atle
> ps: hopefully my "drawing" looks good after I post this
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the Serdev
mailing list