If you use uac_replace_from in a branch route then the changes are specific to 
that branch. If the call fails the header will be reverted and can be modified 
again in another branch.

Ben Newlin

From: 
<users-boun...@lists.opensips.org<mailto:users-boun...@lists.opensips.org>> on 
behalf of Søren Andersen <s...@stofa.dk<mailto:s...@stofa.dk>>
Reply-To: OpenSIPS users mailling list 
<users@lists.opensips.org<mailto:users@lists.opensips.org>>
Date: Wednesday, January 13, 2016 at 8:49 AM
To: "stefano.pis...@omnianet.it<mailto:stefano.pis...@omnianet.it>" 
<stefano.pis...@omnianet.it<mailto:stefano.pis...@omnianet.it>>, OpenSIPS users 
mailling list <users@lists.opensips.org<mailto:users@lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] uac_replace_from multiple times?

Hi,

Thanks for your mail. – Actually I need to send the call out to my client 
without the prefix, and if the client don’t answer the phone the call gets sent 
to another phone number via my ISP.
Do you have a smart solution for this?

/Søren
Fra: users-boun...@lists.opensips.org<mailto:users-boun...@lists.opensips.org> 
[mailto:users-boun...@lists.opensips.org] På vegne af Stefano Pisani
Sendt: 13. januar 2016 14:37
Til: OpenSIPS users mailling list 
<users@lists.opensips.org<mailto:users@lists.opensips.org>>
Emne: Re: [OpenSIPS-Users] uac_replace_from multiple times?

No you can't.
Use a variable to store the from and replace it once, just before to send out 
the message.



Il 13/01/2016 14.32, Søren Andersen ha scritto:
Hello,

I’m wondering if it’s possible to use uac_replace_from multiple times? – fx. 
Inbound call gets changed by uac_replace_from and removed the +45 prefix. – But 
sometimes I need to forward the call back to my ISP, and they need to have +45 
in the from header. But if I try to use the function two times the sip headers 
gets invalid  like the below header:

From: 
<sip:12345...@xx.xx.xx.XXsip:+4512345678@1XX.2XX.2XX.3X;user=phone><mailto:sip:12345...@xx.xx.xx.XXsip:+4512345678@1XX.2XX.2XX.3X;user=phone>;tag=c675aa4668ba7a0c3150f682eea7a54b-7701

Perhaps there are a better option to do this?

/Søren





_______________________________________________

Users mailing list

Users@lists.opensips.org<mailto:Users@lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to