You do not need to manipulate core variables. You have to add a header
to pass the source ip to asterisk.
esample append_hf(X-src-ip: $si\r\n)
Il 10/10/2013 02.05, bluerain ha scritto:
Are you sure? Can you tell my which function call in opensips? I know how
to manipulate the core
cool, thx for that, I will try it! Thank you very much for your help!
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Opensip-as-transaprent-inbound-proxy-for-asterisk-tp7588047p7588055.html
Sent from the OpenSIPS - Users mailing list archive at
Just FYI, I tried, I insert your line in the method invite and right before
the routing, Asterisk didn't seem to care. It still care about the prior
Hop IP.
So what I mean is that
from 199.33.33.33 -- opensip 22.55.33.33 (and then I put your line) --
Asterisk server.
Asterisk server identified
the sugestion from Stefano is to you transport the ip information from
opensips to asterisk, when you are in asterisk you get that variable and
validate the customer, if just opensips will talk with asterisk so you dont
need the ip address on asterisk, just in opensips, you made all validation
on
Hi bluerain,
Our production setup is using OpenSIPS as proxy to many Asterisk instances
via load_balancer module.
I can see from the SIP logs on our Asterisk servers the SIP headers sent
from OpenSIPS to Asterisk still contains the original IP (From, Contact,
and the bottom one Via)
Have you
Just FYI
you need to write down some code in asterisk to manage the new header
obviusly
Il 11/10/2013 02.30, bluerain ha scritto:
Just FYI, I tried, I insert your line in the method invite and right before
the routing, Asterisk didn't seem to care. It still care about the prior
Hop IP.
So
