Hi Owen,
I think basically you are right. But referring to your code example, did
you set up the /log_flag/ module parameter correctly? E.g.:
#!define FLT_ACC 1
modparam("acc","log_flag", FLT_ACC)
Greetings,
Paul
On 06.11.2012 00:34, Owen Lynch wrote:
Hi,
I have transaction accounting to
Hi All,
I've got a problem with Kamailio 3.3.2-1.1 on CentOS 6.3 with locally
postgresql 8.4.13-1.el6_3 libraries, connected to a remote
postgresql91-9.1.6-1PGDP.rhel6 server
The presence module tries to insert a record in the presentity table,
with some xml in the body column.
But the body
Daniel,
I am "reading" a lot... However, I can’t still get the “logic” to overcome my
problem using
Kamailio routing logic. I was willing to have a dual-homed Kamailo+RTPproxy on a
single server, where one interface goes to the Internet and another one goes to
my private network. However, th
Then how does it work on kamailio-3.2.x without (explicit) tcp? Anyway, I
will keep this in mind in my further kamailio setups.
On Tue, Nov 6, 2012 at 12:18 AM, Daniel-Constantin Mierla wrote:
> TLS is a security layer in top of TCP, so apparently tcp has to be
> specified as a listening transp
Hi,
I have transaction accounting to RADIUS setup and get the start and stop
events logged to file when a call is made. I want to extend this to also
get CDR logs - call duration etc. To do this I understand I need to
configure the acc module and load and configure the dialog module:
#!define FLD
TLS is a security layer in top of TCP, so apparently tcp has to be
specified as a listening transport layer to make tls work. Starting with
v3.0.0, tls code is in a module, so the core might not initialize tcp if
it does not have afferent sockets. Not sure what would take to make it
work with t
Try using the same version of PostgreSQL client library and server.
I believe the default handling of binary blobs changed between PostgreSQL
8.x and 9.x. This could well explain your problem.
Kamailio works for me with PostgreSQL 9.0 client library and server.
Regards,
Peter
> Hi All,
>
> I'
Hi All,
I've got a problem with Kamailio 3.3.2-1.1 on CentOS 6.3 with locally
postgresql 8.4.13-1.el6_3 libraries, connected to a remote
postgresql91-9.1.6-1PGDP.rhel6 server
The presence module tries to insert a record in the presentity table,
with some xml in the body column.
But the body
Indeed, this is not implemented correctly.
If you fix it, the question is: what should be used if there are SRV
records for UDP and TCP?
AFAIK there is already a configuration option to choose the respective
NAPTR records according to local priority. These config options could be
reused.
S
Hi Daniel,
Thanks for the reply, Ill will study the htable and let you know what
happens.
thanks!
Maurice
On Mon, Nov 5, 2012 at 6:06 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> seems you use round robin algorithm. You can use hash over call id if you
> want that same path is preserved fo
Keeping listen=tls, I also included "listen=tcp:127.0.0.1:5060". On
restart it says,
Listening on
tcp: 127.0.0.1:5060
tls: XX.XX.XX.XX [XX.XX.XX.XX]:5061
Aliases:
*: XX.XX.XX.XX:*
kamailio started.
And now kamctl ps gives,
Process:: ID=0 PID=931 Type=
Hello,
seems you use round robin algorithm. You can use hash over call id if
you want that same path is preserved for same Call-ID value.
If you want to use round robin, you have to use htable to store where
the INVITE was sent first time, and when it comes second time with auth
credentials,
Hello,
can you put also:
listen=tcp:127.0.0.1:5060
?
Cheers,
Daniel
On Mon, Nov 5, 2012 at 9:31 AM, Ramazan Yilmaz wrote:
> Any idea?
> I have shared my tls configuration with you in my previous post, and as I
> said, that configuration works with kamailio 3.2.4. After silence of 4
> days, d
Any idea?
I have shared my tls configuration with you in my previous post, and as I
said, that configuration works with kamailio 3.2.4. After silence of 4
days, do you confirm that it is a bug? If so, how can it be solved? Any
suggestion?
On Thu, Nov 1, 2012 at 4:23 PM, Ramazan Yilmaz wrote:
> I
14 matches
Mail list logo