Re: [SR-Users] dialog: cseq

2013-06-21 Thread Daniel-Constantin Mierla
Hello, some comments inline. On 6/14/13 2:03 PM, Halina Nowak wrote: Proposal for cseq: cseq numbering: --- a/modules/dialog/dlg_handlers.cWed Apr 03 13:33:38 2013 +0200 +++ b/modules/dialog/dlg_handlers.cFri Jun 14 13:39:47 2013 +0200 @@ -220,7 +220,7 @@ cseq = (get_cseq(msg

Re: [SR-Users] Proposal for dialog: DLG_STATE_EARLY

2013-06-21 Thread Daniel-Constantin Mierla
Hello, I have some comments related to the patches, as I couldn't dig much into sources due to traveling constraints. See them inline. On 6/14/13 2:10 PM, Halina Nowak wrote: These modifications were implementated for dialogs having PRACK and UPDATE --- a/modules/dialog/dlg_handlers.cFri

Re: [SR-Users] $DLG_lifetime

2013-06-21 Thread Carlos Ruiz Díaz
Just for the sake of completeness, you can get the dialog duration (equivalent of $DLG_lifetime) using the following construction: event_route[cnxcc:call-shutdown] { $var(duration) = $TS - $dlg(start_ts); xlog("L_INFO", "Call killed after [$var(duration)] sec(s)"); unfor

Re: [SR-Users] unable to set reason phrase with "t_reply" when cause code is 6xx

2013-06-21 Thread Julien Chavanton
I am sorry, please ignore this thread , my problem is introduced by another equipment, I was not tracing directly on the server and I was not suspecting it ! U 2013/06/21 16:19:37.914918 46.46.46.46:5060 -> 50.50.50.50:5060 SIP/2.0 603 My custom reason phrase. On Fri, Jun 21, 2013 at 3:44 PM,

[SR-Users] unable to set reason phrase with "t_reply" when cause code is 6xx

2013-06-21 Thread Julien Chavanton
Hi, I am trying to customize the reason phrase using t_reply. I noticed that we can not set the reason phrase when the code is in the 6xx range Kamailio TM is setting the reason phrase to "unknown" or to a default one. For example : t_reply("603","My custom reason phrase"); Will send

Re: [SR-Users] $DLG_lifetime

2013-06-21 Thread Federico Cabiddu
Thanks! I'll have a look on this too. Regards, Federico On Fri, Jun 21, 2013 at 2:43 PM, Carlos Ruiz Díaz wrote: > Maybe cnxcc module can help you [1]. > > If you need to set a time limit you could use cnxcc_set_max_time() and > when the call times out, an event route is called. > > [1] http:

Re: [SR-Users] $DLG_lifetime

2013-06-21 Thread Carlos Ruiz Díaz
Maybe cnxcc module can help you [1]. If you need to set a time limit you could use cnxcc_set_max_time() and when the call times out, an event route is called. [1] http://kamailio.org/docs/modules/devel/modules/cnxcc.html Regards, Carlos On Fri, Jun 21, 2013 at 8:30 AM, Federico Cabiddu < feder

Re: [SR-Users] $DLG_lifetime

2013-06-21 Thread Federico Cabiddu
Hi Daniel, thank you for your answer. I tried to catch the BYE with event_route[dialog:end] but I'm facing another problem. When the timeout for the dialog is reached Kamailio correctly sends a BYE to the caller and to the callee but in the logs I see this: DEBUG: dialog [dlg_timer.c:240]: start w

[SR-Users] Regarding Instant messaging using TCP on Kamailio 3.3

2013-06-21 Thread Sunil Chandrasekharan
Hi All Today i could find some information from the logs. When i tested the command : sudo kamcmd core.tcp_list I get 2 connection ( with 2 users regitred with TCP) But when i try to send message from User 2 to User 1, i see that 1 more connection is added. But here the port is confusing. becua

Re: [SR-Users] Info and support for Kamailio

2013-06-21 Thread Stoyan Mihaylov
We use Kamailio - to register users and load balancing. And Asterisk servers to process calls. In Asterisk - I made sip friend with authorization by IP - and all calls from Kamailio are accepted. In Kamailio - all calls from Asterisk are also accepted. I hate products with Asterisk - for me they ar

Re: [SR-Users] Kamailio: MI Command: 'trusted_dump' and 'trusted_reload'

2013-06-21 Thread Sergey Okhapkin
Hmm... trusted_dump and trusted_reload work OK to me. Kamailio compiled from git a week ago. On Friday 21 June 2013 10:59:54 José Luis Millán wrote: > Hi, > > I'm using 'allow_trusted()' from Permissions module without a problem in a > Kamailio 4.0 routing logic. It does just work, but the MI co

[SR-Users] Fwd: Call breaks after 32 seconds (Martin Mou?ka)

2013-06-21 Thread Eduardo Lejarreta
Good morning Martin. RFC3261 says: " [Page 85] RFC 3261SIP: Session Initiation Protocol June 2002 ... If the server retransmits the 2xx response for 64*T1 seconds without receiving an ACK, the dialog is confirmed, but the session SHOULD be terminated. This

Re: [SR-Users] Kamailio: MI Command: 'trusted_dump' and 'trusted_reload'

2013-06-21 Thread Andreas Granig
Hi, On 06/21/2013 10:59 AM, José Luis Millán wrote: Hi, I'm using 'allow_trusted()' from Permissions module without a problem in a Kamailio 4.0 routing logic. It does just work, but the MI command 'trusted_dump' tells me that the module is not in use: Seems like there is an issue with the rpc

[SR-Users] Kamailio: MI Command: 'trusted_dump' and 'trusted_reload'

2013-06-21 Thread José Luis Millán
Hi, I'm using 'allow_trusted()' from Permissions module without a problem in a Kamailio 4.0 routing logic. It does just work, but the MI command 'trusted_dump' tells me that the module is not in use: ''' server:/home/jmillan# kamctl fifo trusted_dump 500 Trusted-module not in use ''' Doing a 'tr

[SR-Users] Serial forking with equal q-value

2013-06-21 Thread Juha Heinanen
Jan Gaida writes: > I have serveral servers who are registered with the same AOR in Kamailio. > Every server registers with a Q-value indicating its availability. When a > user sends an INVITE request through Kamailio to that AOR, Kamailio should > send the request to the server with the best Q-va

[SR-Users] Serial forking with equal q-value

2013-06-21 Thread Jan Gaida
Good morning, I have serveral servers who are registered with the same AOR in Kamailio. Every server registers with a Q-value indicating its availability. When a user sends an INVITE request through Kamailio to that AOR, Kamailio should send the request to the server with the best Q-value. Using t