Hey,
On 21.09.2011 14:58, Phillman25 Kyriacou wrote:
> How can i increase log verbosity to "debug" level? Do i change the below
> debug values?
You just need to change the "debug" parameter. It's gotta be "3" in SIP
Router to get DBG-level verbosity (the most noisy level).
You can also change t
Hey Timo
How can i increase log verbosity to "debug" level? Do i change the below
debug values?
### Global Parameters #
#!ifdef WITH_DEBUG
debug=2
log_stderror=yes
#!else
debug=2
log_stderror=no
#!endif
memdbg=5
memlog=5
Can i use the module sip trace to produce a trace or would y
Hey,
On 21.09.2011 14:16, Phillman25 Kyriacou wrote:
> Yes the mysql replication is basically used to update the standby server
> of new mysql entries in case of a switchover the secondary server will
> be updated in terms of dialog restoration, dialplan update, CDR's etc...
>
> I'm pretty sure
Hey Timo
Yes the mysql replication is basically used to update the standby server of
new mysql entries in case of a switchover the secondary server will be
updated in terms of dialog restoration, dialplan update, CDR's etc...
I'm pretty sure that all messages belonging to a specific dialog reach
Hey Phillip,
On 21.09.2011 13:53, Phillman25 Kyriacou wrote:
> I tried what you told me below, however i'm still getting the same result.
> Just to give you more details on my scenario i have 2 kamailio servers
> running heartbeat for high availability on a virtual ip as well as mysql
> MASTER-M
Hi Timo
I tried what you told me below, however i'm still getting the same result.
Just to give you more details on my scenario i have 2 kamailio servers
running heartbeat for high availability on a virtual ip as well as mysql
MASTER-MASTER replication setup. All traffic is sent on this virtual i
Hey,
On 20.09.2011 15:23, Phillman25 Kyriacou wrote:
> Hey Timo
>
> Thanks for your email.
> I apologise i never copied the config properly. I missed a } to close
> the if statement.
> You can see that the route(WITHINDLG); is called for all requests from
> this config.
>
>
>
># MANA
Hey Timo
Thanks for your email.
I apologise i never copied the config properly. I missed a } to close the
if statement.
You can see that the route(WITHINDLG); is called for all requests from this
config.
# MANAGE ALL DIALOGS
#===
Hey Phillip,
On 20.09.2011 13:48, Phillman25 Kyriacou wrote:
> Thanks for your email.
>
> Yes dlg_manage(); has to now be called on INVITE and BYE/CANCEL messages.
> Where would i have to call loose_route()? Only on INVITE?
On *all* in-dialog requests, i.e., all requests which contain a To tag.
Hey Timo
Thanks for your email.
Yes dlg_manage(); has to now be called on INVITE and BYE/CANCEL messages.
Where would i have to call loose_route()? Only on INVITE?
My configuration did not change between 3.1.2 and 3.1.5.
Call flow example:
==
Cisco PGW ===> Kamailio 3.1.5 ===> VOIP
Hey Phillip,
you probably forgot to keep the mailing list in CC, I'll do that for you.
On 19.09.2011 08:43, Phillman25 Kyriacou wrote:
> You are right.
>
> I added the function dlg_manage(); when there is a BYE or CANCEL and now
> its working perfectly. Before i had this function defined only o
Hey Phillip,
after looking closer at what has been reported to me initially, your
case may be different after all.
Could you possibly use "kamctl fifo dlg_list" to check what state the
majority of dialogs that should be terminated in your opinion are in?
Being given the reference counter should b
Hi Timo
Thanks for the update!
Regards
Phillip
On Fri, Sep 16, 2011 at 3:09 PM, Timo Reimann wrote:
> Hey Phillip,
>
>
> On 16.09.2011 13:35, Phillman25 Kyriacou wrote:
> > Hello
> >
> > I have been facing an issue where the dialog module is showing calls as
> > being active when in fact the c
Hey Phillip,
On 16.09.2011 13:35, Phillman25 Kyriacou wrote:
> Hello
>
> I have been facing an issue where the dialog module is showing calls as
> being active when in fact the call has already been completed long ago
> and this is giving wrong number of concurrent calls on our SNMP work
> stati
Hello
I have been facing an issue where the dialog module is showing calls as
being active when in fact the call has already been completed long ago and
this is giving wrong number of concurrent calls on our SNMP work station
(CACTI) when polling the data from Kamailio. I realized this only starte
15 matches
Mail list logo
