Hi Juha, I need to manually set the ruri_user_avp because next_gws() will set the avp _only_ from REQUEST_ROUTE. Since I didn't called the next_gws() function from the REQUEST_ROUTE, the avp is not there. Being in a FAILURE_ROUTE, the avp is _only_ checked and an error probe is printed out. That's why I manually set the ruri_user_avp.
And seems to work ok, except that I have an issue with the RURI that is set on the outgoing INVITE due to a wrong length for the param: params=<transport=udp>(16) (16) should be (13) I'm not familiar with the parser and that's why I asked here. Maybe I'm the only one trying this scenario ... Regards, Ovidiu Sas On 3/14/07, Juha Heinanen <[EMAIL PROTECTED]> wrote:
Ovidiu Sas writes: > In the failure route, lcr is used to route the call via the gws, but > because Icr is invoked first time in a failure route, we need to > manually set the ruri_user_avp. load_gws() is setting gw_uri_avp and next_gws() is setting ruri_user_avp. -- juha
_______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
