Hi,
Is there an option to prevent this behavior with mediaproxy?
opensips: 10.20.20.159 and 10.20.30.159
UACs: 10.20.20.25 and 10.20.20.26
UAS: 17.17.17.167
You have something wrong on you opensips.cfg, for sure ... We have lot
of UAC's working on that scenario you described, without any
Uwe Kastens escribió:
I was not able to get it up and running with use_media_proxy and
end_media_session, since the mediasession was ended, if a BYE for the
2nd branch arrived.
That could only occurs if you get something wrong with the branches. For
sure :-)
I changed a lot in my script
Raúl Alexis Betancor Santana schrieb:
Uwe Kastens escribió:
I was not able to get it up and running with use_media_proxy and
end_media_session, since the mediasession was ended, if a BYE for the
2nd branch arrived.
That could only occurs if you get something wrong with the branches. For
Uwe Kastens escribió:
Yes, I am sure about this. Is there any good tutorial out there?
No, as far as i known, only the docs about how branches should work.
no, sorr, a typo, should be:
new:
route[1] {
...
engage_media_proxy();
...
t_on_branch(1);
t_on_reply(1);
route(3),
...
}
