omg! of course. thx!
вт, 4 февр. 2020 г. в 18:54, Bogdan-Andrei Iancu :
> Hi Anton,
>
> by default, the module does auto restore of the FROM/TO hdr. The restoring
> is done in the traffic flowing in the opposite direction than the initial
> request. So, the uac_restore_xx() is NOT an uac_undo_xx(
Hi Anton,
by default, the module does auto restore of the FROM/TO hdr. The
restoring is done in the traffic flowing in the opposite direction than
the initial request. So, the uac_restore_xx() is NOT an uac_undo_xx() !
As I understand, you do serial forking and for you want to do different,
Dlg_manage() maybe?
On Tue, 4 Feb 2020 at 14:40, Антон Ершов wrote:
> Hello friends
> Help me to understand. In request_route i make replace from and to fields.
> After an unsuccessful attempt to invite, I try to direct the call to
> another place and again I need to replace the from and to fiel
Hello friends
Help me to understand. In request_route i make replace from and to fields.
After an unsuccessful attempt to invite, I try to direct the call to
another place and again I need to replace the from and to fields. But
instead of replacing, new values are simply added
route {
...
Hi Bogdan,
Thank you very much for the explanation, I haven't understood that the
changes made in the main branch is inherited by the new ones.
I'll change my logic to concentrate the changes in the Branch route, and
provide a feedback to the list.
Thank you very much!
Antonio Anderson Souza
Vo
Hi Bogdan,
I've changed mu script to execute all of the uac_replace only on branch
route, and it's working perfectly.
Thank you very much for the help.
Best regards,
Antonio Anderson Souza
Voice Technology
http://www.antonioams.com
On Thu, Jun 10, 2010 at 5:59 PM, Antonio Anderson Souza <
ant
Hi Antonio,
OpenSIPS allows you to do only one TO / FROM change per branch.
Changes you do in main Route are inherited by all future branches
(including default branch 0). Changes you do in branch route will
affect only that branch
Antonio Anderson Souza wrote:
> Dear All,
>
> I'm getting the
Dear All,
I'm getting the From/To header inconsistnet after a uac_replace_from/to, I'm
using uac_replace_from/to one time in the main Route, and and another on a
BranchRoute after got a failure in the first branch.
As i could understand in the UAC documentation it's not possible to call the
repla
Hi Bogdan,
Over the last few days I came across a few other reasons I can't change the
>From header at the stage where this Opensips instance is operating. I won't
be able to test this until I get another lab environment set up. That could
be a while.
Thanks anyway.
- Jeff
On 4/6/09 12:18
Hi Jeff,
I suspect that the callee device is not properly mirroring the RR header
(maybe is converting to lower cases the whole string), which is against
the RFC.
Try to capture the RR in INVITE leaving OpenSIPS and in the BYE received
by OPenSIPS and see if there are any differences between.
Hello,
The uac_replace_from() function seems to be corrupting the To header in at
least some cases.
Here's an example. A BYE comes in from a PSTN gateway with the following
headers:
To: "Anonymous" ;tag=as12c6b8f1
Route:
After passing through Opensips, the To header reads (TN obfuscated for
11 matches
Mail list logo
