Hi All,
Currently trying to work out the best way to keep track of how many calls are being sent to any given dispatcher destination.
I remember being able to do this years ago with the load balancer module in OpenSIPS: opensipsctl fifo lb_list.
Dispatching algorithm '10' seems to be the best fit for my requirements, as I'm essentially wanting to send calls to a large quantity of FreeSwitch docker containers acting as fax receiving nodes.
Equal weight, just filling them in some balanced fashion.
Any hints or ideas would be much appreciated!
Kind regards,
Tim Bowyer
I experienced issue with kamailio after some time of uptime.
Could you suggest way to enable debug output (equivalent of -ddd options
for kamailio executable) for running daemon?
May be using kamcmd?
Sergey
Hello,
I am starting a discussion here about my plans to do a bit of
refactoring to dispatcher module and gather some feedback if people
think of other improvements.
1) First is about moving from using avps to xavps. It should simplify at
least the config in terms of modparams, but also makes it more coherent
in storing the details of destination record for serial forking.
Practically, from a bunch of avp parameters, there will be one to set
the root xavp name, and the old "avps" will be fields inside the xavp.
2) The second is about the attributes field. I am considering to add the
option to load additional attributes from dedicated columns when using
database. So besides the attrs column, one can specify via a mod param
additional columns to be loaded and added to attributes, like:
modparam("dispatcher", "xattrs", "weight,socket,maxload")
The attributes string will be the value of "attrs" column concatenated
with "weight=val1;socket=val2;maxload=val3" (the valX being the
corresponding values in those columns).
This should make easier the management of the database records. For the
option with a text file, no changes will be done.
3) Anything else that one thinks would be good to add to dispatcher?
Cheers,
Daniel
PS. I wrote to both sr-dev and sr-users, to get the attention of the two
communities. However, you can reply only to sr-users (larger community)
if you are not on sr-dev, because this discussion is about features of
the module, not technical aspects of coding.
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
First compile Kamailio 5.1 binaries and start the services with Kamailio
4.x IMS configuration files. You need to remove few of the deprecated
modules. Then compare the working configuration with 5.X IMS cfg files.
You can use OpenIMS HSS application. Configuration is straight forward.
Calls can be tested using Boghe IMS client.
Regards,
Uts
Hello,
not much into IMS myself, and I see you somehow sorted out the Kamailio
part, but in case it helps, you can find sample configuration files in
the source code tree at misc/examples/ims/
As for FHOSS, I am not sure if that project is active/maintained. Maybe
other guys here using IMS extensions can comment more.
Cheers,
Daniel
On 05.04.18 17:37, Roi Arias Salve wrote:
>>* Hi all.
*>> >>* I would like to thank you all the documents you have to install a
*>* Kamailio server. It’s quite easy and fast.
*>> >>* Currently I’m working on Azure, witha Debian 9 OS, and I’d followed
*>* the instructions to install the Kamailio OPENSER, and everything Works
*>* perfect.
*>> >>* But now I’m stuck on my next step. I would like to install all the IMS
*>* components, P-cscf/I-cscf/S-cscf/Fhoss following this document
*>* https://www.kamailio.org/wiki/tutorials/ims/installation-howto
<https://www.kamailio.org/wiki/tutorials/ims/installation-howto>
*>> >>* But, I have no success. Maybe I’ve a mistake on the selection for the
*>* Debian OS installed on the server. I say this because of this sentence:
*>>* “ *Note: This document is work in progress and yet unfinished!*
*>>* This is a short installation howto for Debian Wheezy (stable).
*>>* “
*>> >>* So, I asume that maybe here I have a problem with the OS version, I’ll
*>* try to summarize where I have problems:
*>> >>* 1.- I’ve installed the , P-cscf/I-cscf/S-cscf not a problem.
*>> >>* 2.- I am not able to follow this steps related to the repository:
*>> >>* First, install the Key for our repository:
*>>* wget -O - http://repository.ng-voice.com/PublicKey
<http://repository.ng-voice.com/PublicKey> | apt-key add -
*>>* Then add the repository to your “/etc/apt/sources.list”:
*>>* echo "deb http://repository.ng-voice.com
<http://repository.ng-voice.com/> jessie ims rtpproxy" >>
*>* /etc/apt/sources.list
*>> >>* and also I have problems with this action over the repository
*>> >>* Note: You will need to add the “non-free” packages to your repository:
*>>* deb http://ftp.de.debian.org/debian
<http://ftp.de.debian.org/debian> lenny main non-free
*>* deb http://security.debian.org/ <http://security.debian.org/>
lenny/updates main non-free
*>> >> >> >>* 3.- I decided to install directly the modules from an apt-get
*>* install action, because I followed the instructions on the Log created
*>* on the Kamailio starting box, where you can find all the steps related
*>* to IMS modules, and the suggestion there it is to compile your own
*>* modules. On this step I detected a problem related with the dialog_ng
*>* module, according to the .log document on the Starting box, you have
*>* to include all the modules before you execute the make all instruction:
*>> >>* modify modules.lst for included modules and excluded modules (use
*>* saved file)
*>>* - include: ims_auth ims_charging ims_icscf ims_isc
*>* ims_qos ims_registrar_pcscf ims_registrar_scscf ims_usrloc_pcscf
*>* ims_usrloc_scscf dialog_ng cdp cdp_avp
*>> >>* 4.- After this issue, I tried to install FHOSS, but here I can’t go
*>* further, I am not able to compile it, neither doing my own compilation
*>* following this step
*>> >>* ant compile deploy | tee ant_compile_deploy.txt
*>> >>* nor following
*>> >>* apt-get install openimscore-fhoss
*>> >>* I was no table to get connected to the repository, so I can’t
go further.
*>> >>* I’m sorry for all this information, can anyone help? Any suggestion?
*>> >>* Regards
*>>* Roi
*>> >>>* <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>>
*>* Libre de virus. www.avast.com <http://www.avast.com>
*>* <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>>
*>>>>>* _______________________________________________
*>* Kamailio (SER) - Users Mailing List
*>* sr-users at lists.kamailio.org
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
*>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
*
--
Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
Any idea in this regards?
I understood it's structure of HI2Operations as ASN.1 IRI-HI2, I attached it.
I think i should convert SIP signalling flow to this structure for transmission.
Is it right way that i am doing?
With Regards.Mojtaba
On Thu, Apr 26, 2018 at 12:50 PM, Mojtaba <mespio(a)gmail.com> wrote:
> Hello,
> The declaration of details are in 3GPP TS 101-671 Annex D.5 (ASN.1
> description of IRI (HI2 interface)).
> I need a sample packet of HI2Operations for underestanding, so that
> i'll develop this HI in kamailio.
> With Regards.Mojtaba
>
>
> On Thu, Apr 26, 2018 at 11:20 AM, Daniel-Constantin Mierla
> <miconda(a)gmail.com> wrote:
>> Hello,
>>
>> can you provide more details or references (web links) about the operations
>> you want to do? Like what sip message comes to kamailio and what you need to
>> change to it.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 25.04.18 06:00, Mojtaba wrote:
>>
>> Hello.
>> I need to use HI2Operations for transfering IRI-Parameters in kamailio.Dose
>> anybody have experience in this regards?
>> Thanks.
>> Mojtaba
>>
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users(a)lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierla
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>
>
>
> --
> --Mojtaba Esfandiari.S
--
--Mojtaba Esfandiari.S
Hi, I'm trying to use the TOPOS module to solve some MTU issues we have (we
have multiple kamailio servers in our architecture and route/via headers
are becoming a problem)
The module seems to work but I'm getting these errors on the log:
0(94) ERROR: topos [tps_storage.c:480]: tps_db_insert_dialog(): No
database handle - misconfiguration?
0(94) ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to
store
I get these errors for some time after running kamailio and then they stop
appearing.
Data is inserted on topos_d and topos_t on the db, so I'm not sure what the
error is referring to.
Any idea?
Thanks,
Enrico.
hello all
we have seen that when an OPTIONS is sent with CSep: 0 OPTIONS, message
is not parsed.
Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]:
ERROR: <core> [core/parser/parse_cseq.c:61]: parse_cseq(): no method found
Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]:
ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]:
ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]:
ERROR: <core> [core/parser/msg_parser.c:331]: parse_headers(): bad
header field [CSeq: 0
Jun 4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]:
WARNING: <core> [core/receive.c:198]: receive_msg(): parsing relevant
headers failed
as far i see in rfc3261
"The
sequence number value MUST be expressible as a 32-bit unsigned
integer and MUST be less than 2**31."
i don't know if you already discussed about this, but do you think it
would be something to fix?
best regards and thanks a lot
david escartin
Hello,
Kamailio SIP Server v5.1.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.1, that
includes fixes since the release of v5.1.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.1.x. Deployments running previous v5.1.x
versions are strongly recommended to be upgraded to v5.1.4.
For more details about version 5.1.4 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2018/06/kamailio-v5-1-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
Hi List,
I have this warning message in kamailio log when Kamailio handle an OPTIONS
message with topos module enabled (I am using Kamailio 5.1.2):
WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address
- do record routing for all initial requests
In my config file, OPTIONS message is handled this way:
if ( is_method("OPTIONS") ) {
t_newtran();
record_route();
t_reply("200","OK");
exit;
}
I have found this issue on Github but it is closed and I am not sure what
was the solution: #1483 <https://github.com/kamailio/kamailio/issues/1483>
My server receives 4 OPTIONS messages every 10 seconds that give as many
warning in my log file. What could I do to get rid of them?
Thanks,
Minh