Here it is.. We are trying to keep the prefix, in a header or a avp or something..
So we want to use the prefix to log a certain gw used..
Usually calls come from A to SER to other Term boxes.
The problem is once I load_gw() then I cannot use the values.
EX: on invite I do some checking , then load_gw..
If gw is box X.. then we add a prefix 2312 lets say.
Upon reply I cannot get that value back even in $ruri
Although I can set anything in the invite before leaving .
Also tried add_rr_param but no go..
Any ideas ?
Basically on :
onreply_route[1] {
if(is_method("INVITE") && ($rs==183) ) {
# DO STUFF
I need to access the gateway it used from here..
}
}
This will never work, the other server will never reply to your INVITE with another INVITE, it will reply with 100 trying, ACK, 200 OK, 186 (? ringing) etc..
Im pretty new to ser so im not sure how to help you, but any headers added to your outgoing INVITE will NOT be repeated back to you in the onreply route in the sip packet. Can you use flags? They can survive across branches. I think AVP's can too (though im not sure).
Sorry I cant be much help.
________________________________
From: users-bounces@openser.org [mailto:users-bounces@openser.org] On Behalf Of Frank Cases Sent: 25 June 2007 06:04 To: users@openser.org Subject: [OpenSER-Users] LCR and replies GW
Here it is.. We are trying to keep the prefix, in a header or a avp or something..
So we want to use the prefix to log a certain gw used..
Usually calls come from A to SER to other Term boxes.
The problem is once I load_gw() then I cannot use the values.
EX: on invite I do some checking , then load_gw..
If gw is box X.. then we add a prefix 2312 lets say.
Upon reply I cannot get that value back even in $ruri
Although I can set anything in the invite before leaving .
Also tried add_rr_param but no go..
Any ideas ?
Basically on :
onreply_route[1] {
if(is_method("INVITE") && ($rs==183) ) {
# DO STUFF
I need to access the gateway it used from here..
}
}
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________