Hi,
I have a SIP server with TLS + client certificate based authentication.
The server is listening for SIP(UDP) on port 5060, and for SIPS(TLS) on port
5061)
The client certificate based authentication is enforced on port 5061.
I would like to fire up MSILO and face now a strange problem:
At
Hi Daniel!
I applied now the source ip check and it is working!
Thanks a lot!
regards
Marc
From: proy...@hotmail.com
To: sr-users@lists.sip-router.org
Date: Tue, 3 Jun 2014 21:38:32 +
Subject: [SR-Users] MSILO - dumped messages get duplicated
Hi,
I have a Kamailio 3.2 setup up an
Hi,
Can anybody help me with these duplicate messages?
I guess the first message should be removed from the db, since it got a reply
202.
Despite that, it end up again in the db.
Can you help me what I am doing wrong?
Many thanks
Marc
From: proy...@hotmail.com
To: sr-users@lists.sip-router.o
Hi,
I have a basic MSILO setup up and running.
For the moment every time the client sends a REGISTER, m_dump() is called.
I would like to achieve the following:
The clients are registering with either 200 or 300 sec expiration time.
I would like to dump the messages only when the client is re
Hi,
I have a Kamailio 3.2 setup up and running.
Recently I configured msilo for offline message store. Essentialy the setup
runs fine.
Messages to users without location info getting stored.
In case the user has location info, but cannot be reached, I made
failover_route, so the messages gett
Hi!
I have an up and running msilo config with kamailio 4.0.4.
However, all the queued messages are delivered with a prefix "[Offline message
- (date)(time)]".
Non queued messages are delivered unchanged.
Is there a way I can remove this prefix, so also queued messages get delivered
unchanged?
Hi!
I have question concerning TLS module. I would like to enable TLS 1.2 protocol.
As I understand the TLS module is compiled with openssl, which as far as i know
has TLS 1.2 support since openssl 1.0.1.
I am wondering if there is way to enable TLS 1.2 on the TLS module?
Many thanks
Marc
Hi!
I have a running msilo config. However, messages remain in the db after after
successful delivery, and get removed at the next clean period.
Unfortunatelly, this makes support cases dificult, as we do not see from the db
which messages are delivered and which are not.
My goal is is either
Hi!
I Have a questions concerning t_realy() and failure route.
If the t_realy() is not successful, it makes 12 re-tries before failure route
is called.
Can you help me, how can I lower the number of retries before move to failure
route?
My goal is to make 3 re-tries and then call failure r
"OK");
}
exit;
}
else{
m_store("$ru");
sl_send_reply("200", "OK");
}
exit;
}
but i have still the same behaviour.
Can you help me, what do I wrong?
Many thnaks
Marc. M
10 matches
Mail list logo