"Just make sure if a user fakes the internal headers, that they are not
able to exploit something in your setup"
Hey,
I am using a few custom headers. All the custom headers , except the NAT
one, are authenticated using IP, if the IP doesn't match, the packet is
rejected ( or dropped ). (
If the BYEs are genuine retransmissions, they should be dampened using
t_check_trans() before they are processed by TM and therefore ACC.
On 07/09/2010 08:03 AM, Maciej Bylica wrote:
Dear ALL,
I have configured Kamailio 1.5 from svn with radius (radiusclient-ng)
support for acc.
All seem to w
Dear ALL,
I have configured Kamailio 1.5 from svn with radius (radiusclient-ng)
support for acc.
All seem to work okay, except one thing.
>From time to time I am receiving following radius error (debug from
radius server on different ip)
Fri Jul 9 12:22:58 2010 : Error: rlm_sql (sql): Couldn't up
On 07/09/2010 05:48 AM, Daniel-Constantin Mierla wrote:
On 7/8/10 2:07 PM, Alex Balashov wrote:
Even if it didn't, just add your own RR header.
when you know exactly the inbound/outbound interfaces, yes you can add
yourself the rr headers with textops and don't call rr.
rr has the advantage
On 7/8/10 2:07 PM, Alex Balashov wrote:
Even if it didn't, just add your own RR header.
when you know exactly the inbound/outbound interfaces, yes you can add
yourself the rr headers with textops and don't call rr.
rr has the advantage of adding the rr with outbound local IP in cases
such
On 7/8/10 6:44 PM, Klaus Darilion wrote:
Am 08.07.2010 18:10, schrieb Daniel-Constantin Mierla:
Hello,
On 7/8/10 5:59 PM, Matteo Campana wrote:
Hi all,
I'm using kamailio 1.5 with TLS module.
I need to make ENUM query and get NAPTR record.
> From NAPTR lookup, I'd like to relay my SIP Inv
To use TLS you have 2 choices:
1. Let Kamailio decide: That means you only specify a domain and
Kamailio will do NAPTR lookups and uses the most protocol with highest
priority (thus TLS NAPTR should have highest priority)
2. Force TLS: Kamailio differs between request URI (RURI, $ru) and
des
