[prev in list] [next in list] [prev in thread] [next in thread]
List: openser-users
Subject: [Users] #DEFINE equivalent?
From: mahesh () aptela ! com (Kanakatti Mahesh Subramanya)
Date: 2005-08-30 19:05:31
Message-ID: 431492E2.70506 () aptela ! com
[Download RAW message or body]
because i didn't think of it?
:-)
cheers, and thanx
Bogdan-Andrei Iancu wrote:
> Kanakatti Mahesh Subramanya wrote:
>
>> I totally agree.
>>
>> Personally, I've been ripping out large chunks of my config file, and
>> replacing it with varioud avpops based stuff - it may be *slightly*
>> more convoluted, but it is completely database configurable, and
>> hence easier to maintain
>>
>> re: rr, its actually neither. Its a static, which i'm using to
>> identify NAT'ed clients to account for re-INVITEs
>
>
> why don't you use the append_rr_param() function to added the NAT
> identifier to the RR hdr? do a normal record_route() and if nat is
> detected, add the param
>
> regards,
> bogdan
>
>>
>> cheers
>>
>> Bogdan-Andrei Iancu wrote:
>>
>>> Hi Kanakatti,
>>>
>>> I'm for m4'ing (for the moment) for two reasons:
>>> 1) since we can do it with m4, I prefer to use the cycles for
>>> something still missing;
>>> 2) using dynamic parameters (like via AVPs) reduce the
>>> performance - time to look for the AVP and most critical the
>>> impossibility of calling fixup functions at startup (which will
>>> force to fix params at runtime, for each processing).
>>>
>>> regarding the record_route_preset() - do you use dynamic parameters
>>> or dynamic rr URI?
>>>
>>> regards,
>>> bogdan
>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mahesh.vcf
Type: text/x-vcard
Size: 332 bytes
Desc: not available
Url : http://openser.org/pipermail/users/attachments/20050830/3cf093bc/mahesh.vcf
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic