[Users] Updating call-info...

[Premnath, KN]

Hello Daniel,
	Thank You for all your patient responses.  (t_relay) is working
and a good option.

	But can you tell me how to add "call-info" header in to the
message with "to" party's actual IP-address (I mean the one in location
table's contact column of the "To" username).  This I need for deciding
either to send to a proxy or to a B2BUA call-controller.  Where the
B2BUA call-controller needs to know this data for call-establishing.

	Thank You.
With warm regards,
Premnath,KN 

-----Original Message-----
From: Daniel-Constantin Mierla [mailto:daniel at voice-system.ro] 
Sent: Wednesday, January 10, 2007 8:42 PM
To: Premnath, KN
Cc: users at openser.org
Subject: Re: [Users] Updating call-info...

Hello,

if you just want to use proxy2 as outbound proxy, then use

t_relay("__proxy2_ip__:__proxy2_port__");

An you can keep the RURI untouched in proxy1.

Cheers,
Daniel


On 01/10/07 16:33, Premnath, KN wrote:
> Hi Daniel,
> 	I don't want to store in DB.  Actually what I want is:
> 	1.  I am updating the $ruri and forwarding to proxy 2.
> 	2.  In proxy2 I need a specific information for forwarding the 
> INVITE.  Did not find a place holder to store this specific
information.
> Hence thought will update specific information in the Call-Info header

> when the message is in Proxy 1 and forward the message to proxy 2 by 
> updating the $ruri.
>
> 	Thank you.
> With warm regards,
> Premnath,KN
>
> -----Original Message-----
> From: Daniel-Constantin Mierla [mailto:daniel at voice-system.ro]
> Sent: Wednesday, January 10, 2007 7:56 PM
> To: Premnath, KN
> Cc: users at openser.org
> Subject: Re: [Users] Updating call-info...
>
> Hello,
>
> not sure that this is what you are looking for, but if you want to 
> store the r-uri host part in a special filed of the accounting table, 
> then use the extra accounting feature:
> http://www.openser.org/docs/modules/1.1.x/acc.html#AEN117
> http://www.openser.org/docs/modules/1.1.x/acc.html#AEN314
>
> Cheers,
> Daniel
>
>
> On 01/10/07 10:43, Premnath, KN wrote:
>   
>> Hello,
>>         How to update call-info in openser (for an INVITE sip 
>> message)?  I want the call-info to contain the actual IP-address of 
>> called party. (that we normally do for $ruri).
>>
>>         Thank You.
>> With warm regards,
>> Premnath, KN
>>
>> *The new company Nokia Siemens Networks is expected to start 
>> operations in the first quarter of 2007, subject to customary 
>> regulatory approvals, the completion of standard closing conditions, 
>> and the agreement of a number of detailed implementation steps.**
>>
>> *_Disclaimer:_
>> This e-mail may contain trade secrets or privileged, undisclosed or 
>> otherwise confidential information. If you have received this e-mail 
>> in error, you are hereby notified that any review, copying or 
>> distribution of it is strictly prohibited. Please inform us 
>> immediately and destroy the original transmittal. Thank you for your 
>> cooperation.
>>
>> ---------------------------------------------------------------------
>> -
>> --
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>   
>>     
>
>
> The new company Nokia Siemens Networks is expected to start operations
in the first quarter of 2007, subject to customary regulatory approvals,
the completion of standard closing conditions, and the agreement of a
number of detailed implementation steps.
>
> Disclaimer:
> This e-mail may contain trade secrets or privileged, undisclosed or
otherwise confidential information. If you have received this e-mail in
error, you are hereby notified that any review, copying or distribution
of it is strictly prohibited. Please inform us immediately and destroy
the original transmittal. Thank you for your cooperation.
>
>   


The new company Nokia Siemens Networks is expected to start operations in the first quarter of 2007, subject to customary regulatory approvals, the completion of standard closing conditions, and the agreement of a number of detailed implementation steps.

Disclaimer:
This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.