On Wed, May 29, 2013 at 3:36 AM, Răzvan Crainea <[email protected]> wrote: > Hi, Jock! > > What you should do is to catch the reply in an onreply_route and call the > append_hf() function for the 200 OK reply.
Ah! Of course. Thank you very much Răzvan, works perfectly! - JP > On 05/28/2013 11:21 PM, Jock McKechnie wrote: >> >> I'm sure this isn't this hard, but I must be going crazy because I >> can't figure it out. >> >> I have a real simple call flow that looks like this: >> >> Notifier Box -> OpenSIPS -> Carrier >> >> >> I'd like to RETURN some data to the Notifier from OpenSIPS on the 200 >> OK using a header, but I can only manage to add headers to the >> outgoing proxied leg of the call (from OpenSIP to the Carrier) using >> the append_hf() function. >> >> Am I daft? Or is OpenSIPS doing this on purpose because it breaks RFC? Or? >> >> Boy, I'd sure appreciate some suggestions. I just can't shake the >> feeling I'm doing something really bone-headed. >> >> Cheers; >> >> - Jock >> >> (It'd look something like this: >> Notifier -> OpenSIPS: INVITE >> OpenSIPS -> Notifier: 100 Trying >> OpenSIPS -> Carrier : INVITE >> Carrier -> OpenSIPS: 100 Trying >> Carrier -> OpenSIPS: 183 Session Progress >> OpenSIPS -> Notifier: 183 Session Progress >> Carrier -> OpenSIPS: 200 OK >> <ADD HEADER HERE> >> OpenSIPS -> Notifier: 200 OK, P-New-Header: Here,Dummy. >> . >> . >> etc.) >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
