It is interesting but not easy solution.
Because tls_lookup_cfg accepting only one ip and port...
Another solution can be in [MANAGE_BRANCH] route add next check condition:
```
if ($rP == "TLS") {
$xavp(tls=>server_name) = $rd + ":" + $rp;
$xavp(tls=>server_id) = $rd + ":" + $rp;
}
```
In my case kamailio acts as client to cisco sip tls gateway to make outgoing
calls.
and private_key is not remote server private key it is client private key to
make client authorization on remote server.
Without this cisco close tls connection.
--
You are receiving this because you are subscr
sorry for incorrect formating.
i have made comment using mobile version
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/842#issuecomment-257905413
As i understand from
https://github.com/kamailio/kamailio/blob/master/modules/tls/tls.cfg
# Special settings for the iptel.org public SIP
# server. We do not verify the certificate of the
# server because it can be expired. The server
# implements authentication using SSL client
# certificates so
Hi All.
After some try to configure kamailio 4.4.3 to act as SPI TLS client for Cisco
SIP TLS gateways I have found one issue.
If I do client configuration for tls
[client:10.1.23.19:5061]
verify_certificate = yes
ca_list = /etc/kamailio/CAs/ca1.pem
[client:10.1.23.29:5061]
verify_certificate
Hi, All.
I have some problems with pkg_memory leak.
After each call used private memory of the "udp receiver" process
increases at 2500 bytes.
On test environment I hav set it to 2Mbyte, but it is full after 700 calls.
I need to modify SDP in invite and other packets.
When I do in script
==
