I was thinking of using script variable to hold the source leg information for multi-leg accounting as avp variables will be lost when request is relayed(I'm pushing uri and relaying request in case of call forwarding). Is it safe way or will it create any issues when simultaneous calls are going on.
Hello,
On 06/17/08 14:11, Ruchir wrote:
I was thinking of using script variable to hold the source leg information for multi-leg accounting as avp variables will be lost when request is relayed(I'm pushing uri and relaying request in case of call forwarding). Is it safe way or will it create any issues when simultaneous calls are going on.
the AVPs are not lost when relaying with TM functions. AVPs should be used for this kind of operations.
Script variables are stored in private memory and are persistent per process. The accounting event may happen in a different process than the one that processed the request. Using script variables is not safe.
Cheers, Daniel
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
I'll try to use avps and let you know.
On Tue, Jun 17, 2008 at 5:03 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
On 06/17/08 14:11, Ruchir wrote:
I was thinking of using script variable to hold the source leg information for multi-leg accounting as avp variables will be lost when request is relayed(I'm pushing uri and relaying request in case of call forwarding). Is it safe way or will it create any issues when simultaneous calls are going on.
the AVPs are not lost when relaying with TM functions. AVPs should be used for this kind of operations.
Script variables are stored in private memory and are persistent per process. The accounting event may happen in a different process than the one that processed the request. Using script variables is not safe.
Cheers, Daniel
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
I tested and found that avp variables are lost after relaying the request. My call scenario is like following
1. Call is made 2. Callee has call forwarding so appropriate avp values are loaded. 3. avp for source and destination number are stored for multi-leg accounting 4. request is relayed 5. request comes again to openser 6. avp variable is lost this time
On Tue, Jun 17, 2008 at 5:14 PM, Ruchir ruchir.lists@gmail.com wrote:
I'll try to use avps and let you know.
On Tue, Jun 17, 2008 at 5:03 PM, Daniel-Constantin Mierla < miconda@gmail.com> wrote:
Hello,
On 06/17/08 14:11, Ruchir wrote:
I was thinking of using script variable to hold the source leg information for multi-leg accounting as avp variables will be lost when request is relayed(I'm pushing uri and relaying request in case of call forwarding). Is it safe way or will it create any issues when simultaneous calls are going on.
the AVPs are not lost when relaying with TM functions. AVPs should be used for this kind of operations.
Script variables are stored in private memory and are persistent per process. The accounting event may happen in a different process than the one that processed the request. Using script variables is not safe.
Cheers, Daniel
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
hi guys,
I have the following scenario. I want to use Asterisk as voicemailserver, but need an rtp-Proxy because the my phone speaks srtp. I get SIP-Message from an PBX to openser and RTP Proxy. My question now is, how I can handle this case or how I can forward from rtpproxy to asterisk? just with rewritehostport?
thanks in advance!
regards
Martin
El Miércoles, 18 de Junio de 2008, Martin-Gruber.External@infineon.com escribió:
hi guys,
I have the following scenario. I want to use Asterisk as voicemailserver, but need an rtp-Proxy because the my phone speaks srtp. I get SIP-Message from an PBX to openser and RTP Proxy. My question now is, how I can handle this case or how I can forward from rtpproxy to asterisk? just with rewritehostport?
Hi Martin, you have repeat exactly the already answered question.
First: RtpProxy doesn't handle SIP signalling so when you say "I get SIP-Message from an PBX to openser and RTP Proxy" that is incorrect.
Second: Asterisk doesn't handle SRTP and SRTP is end to end, like RTP, so a RTP proxy can do nothing (think in it as a UDP proxy in fact).
In conclusion: you can speack SRTP with Asterisk since Asterisk doesnt' support it and you cannot use a RtpProxy as intermediary for that purpose.
El Wednesday 18 June 2008 14:52:47 Ruchir escribió:
I tested and found that avp variables are lost after relaying the request. My call scenario is like following
- Call is made
- Callee has call forwarding so appropriate avp values are loaded.
- avp for source and destination number are stored for multi-leg
accounting 4. request is relayed 5. request comes again to openser 6. avp variable is lost this time
Of course. AVP's live for a transaction (and for responses to this transaction is "avp_on_reply" is set to "yes" in "tm" module).
If OpenSer sends a request (client transaction) and this request comes back (maybe a spiral) the new arriving request is a server transaction independent of the first client transaction and of course they don't sahre AVP's.
For this you need adding headers or parameters in the message.
How to retrieve value from header?
On Wed, Jun 18, 2008 at 6:31 PM, Iñaki Baz Castillo ibc@in.ilimit.es wrote:
El Wednesday 18 June 2008 14:52:47 Ruchir escribió:
I tested and found that avp variables are lost after relaying the
request.
My call scenario is like following
- Call is made
- Callee has call forwarding so appropriate avp values are loaded.
- avp for source and destination number are stored for multi-leg
accounting 4. request is relayed 5. request comes again to openser 6. avp variable is lost this time
Of course. AVP's live for a transaction (and for responses to this transaction is "avp_on_reply" is set to "yes" in "tm" module).
If OpenSer sends a request (client transaction) and this request comes back (maybe a spiral) the new arriving request is a server transaction independent of the first client transaction and of course they don't sahre AVP's.
For this you need adding headers or parameters in the message.
-- Iñaki Baz Castillo ibc@in.ilimit.es
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
I just figured out, we can use $hdr(name[N]).
On Wed, Jun 18, 2008 at 6:48 PM, Ruchir ruchir.lists@gmail.com wrote:
How to retrieve value from header?
On Wed, Jun 18, 2008 at 6:31 PM, Iñaki Baz Castillo ibc@in.ilimit.es wrote:
El Wednesday 18 June 2008 14:52:47 Ruchir escribió:
I tested and found that avp variables are lost after relaying the
request.
My call scenario is like following
- Call is made
- Callee has call forwarding so appropriate avp values are loaded.
- avp for source and destination number are stored for multi-leg
accounting 4. request is relayed 5. request comes again to openser 6. avp variable is lost this time
Of course. AVP's live for a transaction (and for responses to this transaction is "avp_on_reply" is set to "yes" in "tm" module).
If OpenSer sends a request (client transaction) and this request comes back (maybe a spiral) the new arriving request is a server transaction independent of the first client transaction and of course they don't sahre AVP's.
For this you need adding headers or parameters in the message.
-- Iñaki Baz Castillo ibc@in.ilimit.es
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
El Tuesday 17 June 2008 13:33:55 Daniel-Constantin Mierla escribió:
Script variables are stored in private memory and are persistent per process. The accounting event may happen in a different process than the one that processed the request. Using script variables is not safe.
I've never used script variables. Just a question: are they like normal $variables ($var(example)) that persist for each OpenSer process? It's not very safe to use $variables since you must be sure of reseting them in each request/response you process before use them or you will get a value set in a previous request/response by the same OpenSer process.
Do script variables share this behaviour?
Thanks.