Oh! Understood.
- Jeff
On Tue, Jun 1, 2021 at 2:42 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> The thing is I _want_ to drop the 302, I don't want to do anything else
> with it.
>
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
>
The thing is I _want_ to drop the 302, I don't want to do anything else
with it.
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Tue, Jun 1, 2021 at 6:46 PM Jeff Pyle wrote:
> In my experience you don't need drop() in the reply route. Just store
> the AV
In my experience you don't need drop() in the reply route. Just store the
AVP and move on. Something like this:
onreply_route[collect_identity] {
if (is_present_hf("Identity")) {
$avp(identity) := $hdr(Identity);
setflag("GOT_IDENTITY");
}
}
If you've armed both the repl
Yes, I see it is documented.
So the reply header is only availanble on the "onreply" route, not on the
"failure" route. That was my problem. I do indeed use an avp to store the
header.
I ended up getting the header on the "onreply" and storing it in an avp,
set a flag and then drop(). I noticed th
It’s documented that it works this way. The message being processed in
failure_route is the original request; in reply_route it’s the reply. [1]
You can use variable context to access the reply from failure_route [2].
Another option would be to extract the header value into and AVP in reply_rout
Yeah, my thing is when i use the failure route i can in theory grab the
response header and ignore the 302 and send to the invite route again to
actually send the call out via do_routing.
What I'm trying to do is:
- On receiving an invite: forward to an endpoint.
- This endpoint will simply reply w
I don't think you're doing anything wrong. I think I found the same thing,
that headers on the reply were available only in a reply route and not in a
failure route. If you know where to look for them to populate the AVP, I
suppose it doesn't matter much.
I haven't looked at the code but I suspe
Thanks Jeff,
MMM, that's strange, I was using it on failure route and the route was
being executed, but the data wasn't there. I put it on the onreply route
and that one is now executed with the data correctly there...
I probably did something wrong.
Thanks again Jeff!
Regards,
David Villasmil
Miha,
First, do you need to use "mtsbc.test.com:5060" in the first
record_route_preset() param? Can you use the IP address of your proxy
instead? FQDNs are legal of course, but outside of MS Teams'
implementation, they're rarely required. It's just another thing to go
wrong. Especially while t
In which route are you trying to use if (is_present_hf("Identity"))? Since
the 302 is both a reply and a "failure", I suggest seeing if it appears in
either the armed onreply_route or failure_route.
I think From is available because it was present in the original request
route.
- Jeff
On Tue,
Anyone has any idea about this? Appreciate your help.
On Mon, 31 May 2021 at 21:11, David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> So weird,
> I can get the From header, but not "Identity"...
>
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +3466944833
Hello
I have an issue and I am unable to find out what is wrong. Incoming
calls are working but when doing outbound call after 200OK, which is
send to Teams I get back ACK and after that Teams do again initial. I
guess this is not ok.
I am doing this for outband calls:
xlog("L_INFO", "rtp
12 matches
Mail list logo
