.
This is useful when you are trying to call to a UA which kamailio still
keeps registration record for, but TCP/TLS connect to this phone is already
gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote:
In general, it happens in our network (as more and more Via
; Mickael Marrache
Subject: Re: [SR-Users] db_mongodb get columns error
Hello,
On 27/04/15 23:46, Daniel-Constantin Mierla wrote:
Hello,
On 22/04/15 14:00, Mickael Marrache wrote:
Hi,
After restarting Kamailio, I got the following errors during the startup:
kamailio[12614]: ERROR
Hi,
I sometimes see the following in the logs:
kamailio[14433]: ERROR: core [tcp_read.c:271]: tcp_read_data(): error
reading: Connection reset by peer (104)
kamailio[14433]: ERROR: core [tcp_read.c:1296]: tcp_read_req(): ERROR:
tcp_read_req: error reading
It looks like Kamailio tries
connection to a phone if there is no active connection.
This is useful when you are trying to call to a UA which kamailio still
keeps registration record for, but TCP/TLS connect to this phone is already
gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote
, it is recommended to not
connect if there is no active connection after location lookup -- see core
functions for tcp.
Cheers,
Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are
looking at using TCP instead of UDP
the top Via with the non-VIP interface although the INVITE is
forwarded to the proxy using the VIP interface.
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Alex
Balashov
Sent: Tuesday, May 05, 2015 3:31 PM
To: Mickael Marrache; sr-users@lists.sip-router.org
Subject
Hi,
We are adding TCP support to our load balancer and for some reason it adds
two record route headers.
The instance have two IP addresses on which it binds: one if the VIP address
and the second is the non-VIP address.
I explicitly set the tcp_source_ipv4 parameter with the VIP
address with:
listen=tcp:1.2.3.4:5060 advertise 1.2.3.4:5060
Cheers,
Daniel
On 05/05/15 15:02, Mickael Marrache wrote:
Here, there are 2 interfaces but only the VIP should be used. Also, the
INVITE exits the same interface it entered (i.e. the VIP) but exits with a
different source port (because
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are
looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:ip:5060
listen=tcp:ip:5060
disable_tcp=no
] Possible bug in TM module
Hello,
On 22/04/15 11:26, Mickael Marrache wrote:
Hi,
I just got the following issue when stopping kamailio.
kamailio[7279]: NOTICE: core [main.c:682]: handle_sigs(): Thank you for
flying kamailio!!!
kamailio[7279]: ERROR: ctl [ctl.c:369]: mod_destroy(): ERROR
Hi,
I just got the following issue when stopping kamailio.
kamailio[7279]: NOTICE: core [main.c:682]: handle_sigs(): Thank you for
flying kamailio!!!
kamailio[7279]: ERROR: ctl [ctl.c:369]: mod_destroy(): ERROR: ctl: could not
delete unix socket /tmp/kamailio_ctl: Operation not permitted
Hi,
After restarting Kamailio, I got the following errors during the startup:
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]:
db_mongodb_get_columns(): field [caller_sock] not found in result iterator
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]:
location record. Given this, (again
iirc), this feature doesn't work with db_mode set to database only.
Cheers,
Daniel
On 20/04/15 10:46, Mickael Marrache wrote:
Didn't know about that, it's interesting.
I'm curious about the load impact of this feature, since keepalives are
generally
Hi,
You need to configure your client to un register when the app is closed.
For that, your client must send a REGISTER with Expires: 0.
Mickael
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
xuefeng zhang
Sent: Monday, April 20, 2015 10:58 AM
To:
Grotti wrote:
Hi,
here you are:
https://tools.ietf.org/html/rfc3665#section-2.4
--
Daniel Grotti
VoIP Engineer
Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
On 04/20/2015 10:10 AM, Mickael Marrache wrote:
Hi,
You need to configure your
GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
On 04/20/2015 10:10 AM, Mickael Marrache wrote:
Hi,
You need to configure your client to un register when the app is closed.
For that, your client must send a REGISTER with Expires: 0.
Mickael
*From:*sr
Hi,
What are the statistics that should be used to monitor a Kamailio instance?
I currently looked at shmem_real_used_size, shmem_used_size,
dialogs_active_dialogs. However, I'm looking for other statistics that
represent the load on the instance.
Thanks,
Mickael
Hi,
I get the following warning when a dialog timeout occurs:
kamailio[18889]: WARNING: dialog [dlg_req_within.c:214]: bye_reply_cb():
inconsitent dlg timer data on dlg 0x7f422986e448 [3547:6673] with clid
'mycvJWgmbmOSD5XQrcStKAKoTfW12XeR' and tags
'C5mlsaZCdTmybNSYgvWr75MBxWa5hVyA'
PM
To: Mickael Marrache; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Inconsistent dlg timer data warning at dialog
timeout
On 15/04/15 15:42, Mickael Marrache wrote:
It looks like it is a real issue since CDRs are not generated on dialog
timeout.
If the dialog
I also confirm the cdr_on_create() [acc_cdr.c:718] function is called since
I can see the debug statement dialog '%p' created!.
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Wednesday, April 15, 2015 3:48 PM
To: sr-users@lists.sip-router.org
Subject: No CDR is written when
Also, I get this warning without two BYEs crossing since the BYEs are
generated by Kamailio and sent to the caller and callee.
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Wednesday, April 15, 2015 4:43 PM
To: 'mico...@gmail.com'; 'Kamailio (SER) - Users Mailing List
Hi,
I'm testing the dialog timeout scenario and I see that no CDR is written.
This is my configuration:
modparam(acc, cdr_enable, 1)
modparam(acc, cdr_expired_dlg_enable, 1)
modparam(acc, cdr_start_on_confirmed, 1)
modparam(acc, cdr_log_enable, 0)
modparam(acc, cdr_on_failed, 0)
Hi,
I'm looking for a way to differentiate between regular hangup and dialog
timeout.
In both case, the dialog:end event is called. Do you know which information
can I use in the event route to differentiate between the two cases?
Thanks,
Mickael
...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Wednesday, April 15, 2015 3:20 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Differentiating between regular hangup and dialog
timeout
Hello,
On 15/04/15 14:02, Mickael Marrache wrote:
Hi,
I'm looking
: Wednesday, April 15, 2015 3:22 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Inconsistent dlg timer data warning at dialog
timeout
Hello,
On 15/04/15 14:04, Mickael Marrache wrote:
Hi,
I get the following warning when a dialog timeout occurs:
kamailio[18889]: WARNING
I'm looking at the dlg_ontimeout function [dlg_handlers.c:1369] and I
understand the code, the DLGCB_EXPIRED callbacks are not called when the
send_bye parameter is set to 1.
I'm looking at the block 1399-1408.
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Wednesday
Hi,
I sometimes get the following errors:
kamailio[16098]: ERROR: core [resolve.c:1693]: sip_hostport2su(): could
not resolve hostname: mycompany.com
kamailio[16098]: ERROR: tm [ut.h:319]: uri2dst2(): failed to resolve
mycompany.com
mycompany.com cannot be resolved using DNS (there is
I created a pull request that I tested using MongoDB.
It works fine.
Let me know if I can help more.
Mickael
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Monday, April 13, 2015 5:13 PM
To: mico...@gmail.com; 'Kamailio (SER) - Users Mailing List'
Subject: RE: [SR
Does Kamailio have a way to determine if to use the TM or SL module to send
the reply?
If yes, maybe the right solution is to modify the REGISTRAR sources to use
it.
I know OpenSIPS has a module called SIGNALING that allows exactly that.
-Original Message-
From: sr-users
Any idea?
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Thursday, April 09, 2015 2:08 PM
To: sr-users@lists.sip-router.org
Subject: RE: Avoiding script writer didn't release transaction warnings
I think understand in which case it happens.
When I receive a REGISTER
Can you think of a case where one wants to reply stateless even if a
transaction exists?
-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Alex Balashov
Sent: Monday, April 13, 2015 9:06 PM
To: Mickael Marrache
Subject: Re: [SR-Users] Avoiding
Hi,
Very short question.
Why the time at which the dialog ended is also included in the CDRs?
There already are the start time and duration.
Is it there to avoid end time computation?
Mickael
___
SIP Express Router (SER) and Kamailio
Hi,
I added your changes to my deployments.
Thanks!
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Friday, April 03, 2015 12:54 PM
To: Mickael Marrache; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Dialog based CDRs and failed dialogs
OK, I
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
the built in fields (e.g. duration), we need to perform queries based on
duration and time and it is not really possible using strings.
I see that the time
List
Subject: Re: [SR-Users] CDR fields are all strings
Hello,
On 13/04/15 11:48, Mickael Marrache wrote:
Hi,
Why are all the CDR fields inserted as strings?
For extra fields, I can understand it is easier to implement. However, for
the built in fields (e.g. duration), we need
Hi,
In my logs, I get a lot of the following warnings:
WARNING: tm [t_lookup.c:1476]: t_unref(): WARNING: script writer didn't
release transaction
I force transaction creation from my script to absorb retransmissions as
soon as possible. I understand that I need to explicitly call
the SL module is used instead). Therefore, I get the
warning every time it happens since the transaction is not released
explicitly.
Should I call t_release just before exiting the block handling the REGISTER?
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Thursday, April 09
14:36, Mickael Marrache wrote:
Hi,
I'm using the ACC module to generate dialog based CDRs and I see that CDRs
are generated even for failed calls.
For example, a CDR is generated for cancelled calls.
At first, I thought that dialog based CDRs are generated only for
successfully
Hi,
I'm using the ACC module to generate dialog based CDRs and I see that CDRs
are generated even for failed calls.
For example, a CDR is generated for cancelled calls.
At first, I thought that dialog based CDRs are generated only for
successfully established dialogs but it doesn't
Hi,
We are deploying a VoIP system based on Kamailio. The system is composed of
load balancers, proxies, registrars, etc
What is the recommended transport protocol to use for internal communication
(i.e. load balancer - proxy/registrar)? We started with UDP but we also
see that Kamailio
, Mickael Marrache wrote:
Hi,
I'm trying to add PUSH support to my system using Kamailio.
When a call is received and the callee has no active registration, a PUSH is
sent to the callee endpoint. In order to send this PUSH, my proxy sends an
HTTP requests to another server that will send the PUSH
.
Is it possible to have a pool of timers fetching from the same message
queue?
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Thursday, March 19, 2015 10:28 AM
To: Mickael Marrache; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Sending PUSH notification asynchronously
Hi,
I'm trying to add PUSH support to my system using Kamailio.
When a call is received and the callee has no active registration, a PUSH is
sent to the callee endpoint. In order to send this PUSH, my proxy sends an
HTTP requests to another server that will send the PUSH.
So, my route
19, 2015 10:00 AM
To: Mickael Marrache; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Timeout after t_suspend and failure route
Have you tried forwarding after the timeout of suspended transaction occurred?
What kind of operations you had in the failure route. Trying to see what
Thanks, it works great!
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Thursday, March 19, 2015 11:56 AM
To: Mickael Marrache; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Sending PUSH notification asynchronously
You can define as many rtimer processes
Hi,
We are currently deploying an entire architecture composed of load
balancers, proxies and media relays. All the components except the media
relays are Kamailio instances. The media relays are RTP proxy instances.
We are trying to determine the hardware requirements for the different
Hi,
When receiving an INVITE, I arm a failure route and set the fr_timer to 30
seconds. After the fr_timer expires, I need to do some operations however I
see the failure route is not executed.
I guess it is related to the fact the INVITE has not been forwarded?
If yes, how can I
Confirmed.
Thanks,
Mickael
On 18 במרץ 2015, at 18:06, Daniel-Constantin Mierla mico...@gmail.com wrote:
Hello,
can't check the code right now, but to confirm, if you use t_on_failure()
before suspending the transaction, isn't executed?
Cheers,
Daniel
On 18/03/15 15:56, Mickael
Thanks Daniel!
Your patch seems to have fixed it…
Mickael
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Wednesday, March 18, 2015 8:54 PM
To: Mickael Marrache; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Timeout after t_suspend and failure route
Hi,
I'm continuously seeing the following WARNING in my logs:
WARNING: db_mongodb [mongodb_dbase.c:454]: db_mongodb_get_columns():
unhandled data type column (instance) type id (10), use DB1_STRING as
default
It looks like the WARNING appears when data is fetched from the location
(): destroying xavp list
(nil)
[31723]: DEBUG: core [receive.c:278]: receive_msg(): cleaning up
Thanks,
Mickael
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Tuesday, February 03, 2015 9:43 PM
To: Mickael Marrache; sr-users@lists.sip-router.org
Subject: Re: [SR-Users] Wrong
can help you to figure out what the issue
is.
Thanks,
Mickael
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Saturday, January 31, 2015 8:32 PM
To: 'Kamailio (SER) - Users Mailing List'
Subject: RE: [SR-Users] Wrong location entries when using usrloc with Mongo
Hi
object.
The match was done on username and ruid for deletion, both of them are missing.
I will look at the mongo api to see if something was set wrong there for the
delete command.
Cheers,
Daniel
On Fri, Jan 30, 2015 at 9:54 AM, Mickael Marrache mickaelmarra...@gmail.com
wrote:
I
Hi,
Thanks for the patch, Kamailio doesn't crash anymore.
However, I'm encountering another issue with usrloc + Mongo, I will write a new
post.
Thanks,
Mickael
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Friday, January 30, 2015 7:22 AM
To: Mickael Marrache
Hi,
I start with no location nor in Mongo, nor in memory. My UA registers
successfully and I can see the location entry in Mongo. Then, I close my UA
which unregisters (by setting Expires header to 0). Then, I open the app
again and a new registration is made.
The entry after first
I forgot to precise that I allow only one contact per AOR.
modparam(registrar, max_contacts, 1)
save(location, 0x04)
From: Mickael Marrache [mailto:mickaelmarra...@gmail.com]
Sent: Friday, January 30, 2015 10:51 AM
To: sr-users@lists.sip-router.org
Subject: Wrong location entries when
Hi,
Is there a way to set a dialog variable when a BYE is received so that it
can be written in a CDR?
I tried as follows but it didn't work:
if (loose_route()) {
..
if(is_method(BYE)) {
if(is_direction(downstream)) {
,
Daniel
On 29/01/15 08:55, Mickael Marrache wrote:
Hi,
When my proxy receives a REGISTER request, it crashes while saving the user
location in MongoDB.
This is the backtrace from the core dump:
#0 0x003f08e32625 in raise () from /lib64/libc.so.6
#1 0x003f08e33e05 in abort
the parameters for usrloc module? Are you using DB_ONLY mode?
Cheers,
Daniel
On 29/01/15 08:55, Mickael Marrache wrote:
Hi,
When my proxy receives a REGISTER request, it crashes while saving the user
location in MongoDB.
This is the backtrace from the core dump:
#0 0x003f08e32625
://kamailio.org/docs/modules/4.0.x/modules/acc.html#idp91080
I hope that helps.
All the best.
Will Ferrer
Switchsoft
On Mon, Jan 26, 2015 at 5:23 AM, Mickael Marrache mickaelmarra...@gmail.com
wrote:
Hi,
Is there a way to write CDRs for failed calls?
I tried calling
Hi,
Is it possible to save user location data in a MongoDB database?
If not, are you guys using p_usrloc in your projects? Can you please give me
some feedback?
Thanks,
Mickael
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
Hi,
When my proxy receives a REGISTER request, it crashes while saving the user
location in MongoDB.
This is the backtrace from the core dump:
#0 0x003f08e32625 in raise () from /lib64/libc.so.6
#1 0x003f08e33e05 in abort () from /lib64/libc.so.6
#2 0x006196f9 in
, related to sending options
keepalives. You might need to enable pinging all contact.
Storing and retrieving records in mongodb should work fine -- report any
issue on mailing list and it will be fixed.
Cheers,
Daniel
On 28/01/15 16:37, Mickael Marrache wrote:
Hi,
Is it possible to save user
Hi,
Is there a way to write CDRs for failed calls?
I tried calling the acc_db_request command from my script, but it inserts a
transaction log not a CDR.
Thanks,
Mickael
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
, Mickael Marrache wrote:
Hi,
Is it possible to write CDRs directly to MongoDB using the new db_mongodb
module?
modparam(acc, db_url, DB_MONGO_URL)
modparam(acc, cdr_enable, 1)
modparam(acc, cdr_extra, . )
modparam(acc, cdr_log_enable, 0)
modparam(acc, cdrs_table, cdrs)
In the acc
Hi,
Is it possible to write CDRs directly to MongoDB using the new db_mongodb
module?
modparam(acc, db_url, DB_MONGO_URL)
modparam(acc, cdr_enable, 1)
modparam(acc, cdr_extra, . )
modparam(acc, cdr_log_enable, 0)
modparam(acc, cdrs_table, cdrs)
In the acc module documentation,
Hi,
I'm trying to use one Kamailio instance as load balancer for multiple
Kamailio instances. The load balancer only performs NAT handling and
dispatching of messages. The other instances handle registrations, routing,
RTP proxy, authentication, etc.
When a REGISTER request is received by
67 matches
Mail list logo
