Hi everybody,
The ability of accessing/processing AVPs in reply route was a long debated and wanted functionality. Finally, OpenSER 1.2.x fixes this.
The new code allows two types of behaviours: - use per message AVPs in reply route - no special synchronization is needed, but there is no persistence outside reply route. - use per transaction AVPS in reply route (as in failure route).
the above behaviours apply to the reply routes triggered by TM. You can control this via the new TM parameter "onreply_avp_mode": http://www.openser.org/docs/modules/1.2.x/tm.html#AEN303
in default reply route only per message AVPs will be available.
regards, bogdan
Great! Are there performance issues due to the locking in the reply route?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
The ability of accessing/processing AVPs in reply route was a long debated and wanted functionality. Finally, OpenSER 1.2.x fixes this.
The new code allows two types of behaviours:
- use per message AVPs in reply route - no special synchronization is
needed, but there is no persistence outside reply route.
- use per transaction AVPS in reply route (as in failure route).
the above behaviours apply to the reply routes triggered by TM. You can control this via the new TM parameter "onreply_avp_mode": http://www.openser.org/docs/modules/1.2.x/tm.html#AEN303
in default reply route only per message AVPs will be available.
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Klaus,
this issue is documented in the TM readme - see the link to the TM parameter.
regards, bogdan
Klaus Darilion wrote:
Great! Are there performance issues due to the locking in the reply route?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
The ability of accessing/processing AVPs in reply route was a long debated and wanted functionality. Finally, OpenSER 1.2.x fixes this.
The new code allows two types of behaviours:
- use per message AVPs in reply route - no special synchronization
is needed, but there is no persistence outside reply route.
- use per transaction AVPS in reply route (as in failure route).
the above behaviours apply to the reply routes triggered by TM. You can control this via the new TM parameter "onreply_avp_mode": http://www.openser.org/docs/modules/1.2.x/tm.html#AEN303
in default reply route only per message AVPs will be available.
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Brilliant!
Thanx for getting this in.
I'm assuming that y'all managed to work around the synchronization issues.
again - brilliant!
cheers ----- Original Message ----- From: Bogdan-Andrei Iancu bogdan@voice-system.ro To: users openser.org users@openser.org, devel devel@openser.org Sent: Friday, February 9, 2007 10:27:29 AM GMT-0600 Subject: [Users] MAJOR FIXUP: avp access in reply route
Hi everybody,
The ability of accessing/processing AVPs in reply route was a long debated and wanted functionality. Finally, OpenSER 1.2.x fixes this.
The new code allows two types of behaviours: - use per message AVPs in reply route - no special synchronization is needed, but there is no persistence outside reply route. - use per transaction AVPS in reply route (as in failure route).
the above behaviours apply to the reply routes triggered by TM. You can control this via the new TM parameter "onreply_avp_mode": http://www.openser.org/docs/modules/1.2.x/tm.html#AEN303
in default reply route only per message AVPs will be available.
regards, bogdan
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Klaus Darilion -
Mahesh Paolini-Subramanya