I have been trying to accomplish a couple tasks with Kamailio over the past
month with no luck. What I need is a bit of one-on-one training with
someone who knows the lay of the land. If you do this kind of consulting
and can use Skype with possibly a shared-screen terminal, please drop me an
email with your rate.
Hello,
I used Kamailio+rtpproxy to record a session and rtpproxy outputs the
following files
long_file_name.a.rtp, long_file_name.a.rtcp, long_file_name.o.rtp,
long_file_name.o.rtcp
http://www.rtpproxy.org/wiki/RTPproxy/FAQ
From the Rtpproxy FAQ above, i tried to extract the audio using
rtpbreak and sox.
rtpbreak -W -r long_file_name.a.rtp
rtpbreak -W -r long_file_name.o.rtp
The above commands generate rtp.0.0.raw, rtp.1.0.raw.
Then when i run sox using
sox --combine merge -r 8k -A rtp.0.0.raw -r 8k -A rtp.1.0.raw -t wavpcm
-s out.wav i get the following errors :
sox: invalid option -- -
sox: -c must be given a number
Is there a switch/anything else that i am missing ?
Thanks in advance,
Regards,
Vikram.
Hi,
Since we installed last version of Kamailio (3.1.4) we have been
experiencing a big problem with REGISTER retransmissions. When the
server receives a retransmitted REGISTER it removes the binding and the
UAC remains unregistered until next refreshing period. I include a PCAP
capture that shows this behaviour.
I am not 100% sure that this problem never happened with older versions.
Has anybody experienced the same problem?
Thanks in advanced.
Alejandro.
Hello Stefan,
On 3/14/11 11:03 AM, Stefan Tiedje wrote:
> Thanks for the answer.
> Maybe I have some older versions of the OPENSER-MIB and the other
> related MIB's since I could not find the counter you pointed at. I'm
> using a MIB browser for reading the MIB's.
> Is the suggested counter "expired dialogs" added in a specific release
> of Kamailio? Which? We use Kamailio 3.0.2.
I used Kamailio and recommend using it sine it has the latest commits
for stability.
However, what I wrote before is pretty much not related to the version.
There is a counter that tracks the processed dialogs, but seems it is
not exported by default through snmpstats module. The statistics counter
is named "processed_dialogs", implemented by dialog module.
You can dump all internal statistics through kamctl or via xmlrpc
command, but probably to export it through snmpstats you may need to
extend the mibs and the code of the module.
I just grepped the sources of snmpstats module to see what dialog
statistics it is exporting:
$ grep -n _dialogs modules_k/snmpstats/* | grep get_statistic
modules_k/snmpstats/alarm_checks.c:83: num_dialogs =
get_statistic("active_dialogs");
modules_k/snmpstats/snmpObjects.c:404: int result =
get_statistic("active_dialogs");
modules_k/snmpstats/snmpObjects.c:424:
get_statistic("active_dialogs") -
modules_k/snmpstats/snmpObjects.c:425:
get_statistic("early_dialogs");
modules_k/snmpstats/snmpObjects.c:443: int result =
get_statistic("early_dialogs");
modules_k/snmpstats/snmpObjects.c:459: int result =
get_statistic("failed_dialogs");
modules_k/snmpstats/snmpObjects.c:508: int num_dialogs =
get_statistic("active_dialogs");
Perhaps when the snmpstats was developed the dialog module didn't export
the statistics counter of "processed_dialogs" and then it was not updated.
Now, what I tried to say is that if the "processed_dialogs" counter is
not available through snmpstats (and it is not now after grepping the
sources) you can get its value from another application through "kamctl
get_statistics all" or XMLRPC command for all of the existing kamailio
releases. Upcoming one we will look to implement the export through
snmpstats as well. If you have time to do it and send us a patch, we
will gladly commit it to source tree in our GIT repository.
Cheers,
Daniel
> Do you have the MIB name for the "expired dialogs" counter. I will
> look for that in my version of OPENSER MIBS.
> Important, do you have a link to where MIB files can be downloaded for
> Kamailio 3.0.2?
> Below follows an excerp from one of the MIB's. Is it old, I don't know?
>
> -- ***********************************************************************
>
> -- OPENSER-MIB: OPENSER MIB
>
> --
>
> -- Date of Creation: Januay 2006
>
> --
>
> -- This MIB provides information related to the OpenSER SIP Router.
>
> --
>
> -- Copyright (c) The Internet Society (2006)
>
> -- Ammendments (c) Soma Networks, Inc. (2006)
>
> --
>
> -- All rights reserved.
>
> -- *****************************************************************
>
> /Stefan
>
> ------------------------------------------------------------------------
> *From:* Daniel-Constantin Mierla [mailto:miconda@gmail.com]
> *Sent:* den 14 mars 2011 10:16
> *To:* Stefan Tiedje
> *Cc:* sr-users(a)lists.sip-router.org
> *Subject:* Re: [SR-Users] OPENSER MIB
>
> Hello,
>
> On 3/14/11 9:42 AM, Stefan Tiedje wrote:
>> Hi,
>> In the Kamailio OPENSER-MIB there is the counter
>> "openserTotalNumFailedDialogSetups". This is a Counter32.
>> The description is:
>> "The total number of calls that failed with an error. The
>> following codes define a failed call:"
>> *Question:*
>>
>> * I'm looking for the corresponding counter to
>> "openserTotalNumFailedDialogSetups" who counts successful
>> Dialog setups of Counter32 type. Does it exist?
>> * If not, does it exist a work around?
>> * Where in the code can the new suggested counter be added?
>> * Something else????
>>
>
> the dialog module counts the number of processed dialogs, see:
> http://kamailio.org/docs/modules/stable/modules_k/dialog.html#id2966360
>
> There is no counter currently inside dialog module exporting exactly
> the number of successfully setup dialogs, it should not be hard to do
> it, though. Using the above and the number of failed and expired
> dialogs, you can actually get the number of successful dialogs.
>
> Dialog module being the one that tracks SIP dialogs, therefore being
> able to count them, now I don't know if snmpstats module exports all
> the counters from dialog module. I setup snmpstats just few weeks ago
> and works perfect on Ubuntu/Debian servers, but I had no need to check
> dialog module counters.
>
> Note that you can get the list of all internal statistics via kamctl:
> - kamctl fifo get_statistics all
>
> Or via XMLRPC if you need them remotely in another application.
>
> Another option is to define your statistics with statistics module.
> Knowing that in SIP a successful call dialog means 200ok reply to an
> INVITE transaction, you can count it in the onreply_route[abc] that
> you arm for relayed transactions with t_on_reply("abc").
>
> Hope these help you,
> Daniel
>
>> Suggestion for the new counter is a name like:
>> "openserTotalNumSucceededDialogSetups". It has a counter32.
>> Description: "The total number of calls that succeeded"
>> I know that there are the counters openserCurNumDialogs,
>> openserCurNumDialogsInProgress and openserCurNumDialogsInSetup but
>> these are of Gauge type who only reflects the current situation.
>> These Gauge counters can't be used together with a Counter32 counter.
>> That don't mix. The calculation done for the counter
>> "openserCurNumDialogsInProgress" should be used where every new
>> dialog setup is added to the new suggested counter. A counter of 32
>> should cover a great deal of connections. These counters are usually
>> read, if used, every 15 minutes or 1 hour.
>> *Rationale:*
>> The reason for the new counter is that a calculation between
>> succeeded and failed dialog setups can be done and be used for SLA
>> agreements. Without this, its hard to make any customer versus
>> provider agreements.
>> /Stefan
>> PS. Ask if anything is unclear and I need an answer rapidly.
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users(a)lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla
> http://www.asipto.com
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
it is time to set the time to release v3.2.0. From my point of view,
testing went very well, considering also that core and main modules were
not touched much during this devel cycle, the most of the efforts were
on new modules and application service components such as presence
server, Lua ...
A convenient date for me will be Tuesday, October 18, 2011, allowing to
work a bit on packaging and docs. If there are other preferences, jump
in this discussion.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hi,
my kamailio server is receiving from some customers 3 identical INVITEs when
call is initiated (separated by 200ms). Those 3 INVITEs are making a big
problem with call_control:
WARNING: call_control [call_control.c:1156]: dialog to trace controlled call
was not created. discarding callcontrol.
That is why, the prepaid limit is not working at all in this case. This way
the user can hack the prepaid protection of the account. Otherwise the
call_control is fuilly functional.
Anybody experienced the similar problem? If so, how to resolve it?
Thanks,
Mino Haluz
Hello
It presents a problem because I do not know how to assimilate the
implementation. Until now we had a design of a proxy to balance out between
several gateway, but it will add another proxy for another service (other
users) and use the same gateway output or perhaps different (although not
that be better if divide or unify the gateway). The problem as I have with
the routing entry, which is not very well how to implement it.
Now we have the design like this:
-GW ----\
/ - CARRIER1
USER ------ KAMAILIO ----- GW ---- +
\ - CARRIER2
-GW ----/
And becomes like this:
-GW ----\
/
- CARRIER1
USER ------ KAMAILIOSERVICE1 ----- GW ---- +
\
- CARRIER2
-GW ----/
-GW ----\
/
- CARRIER1
USER ------ KAMAILIOSERVICE2 ----- GW ---- +
\
- CARRIER2
-GW ----/
Or maybe using the same gateway.
The problem is that each carrier provides DID number (I use the same for
both services). Kamailio had thought to put a gateway between the carriers
and that they did check the service and send it to the corresponding gateway
(in the case of the gateway separately), or put it in the proxy gateway and
making checking for routing to proxy (in the case of using the same
gateway). What would be better? Any recommendations on how to put this into
practice?.
The biggest question that I believe is the routing table, as if this new
proxy routes the traffic into and leaves her in the field via ip, also pass
through the output data (I have doubts whether SIP level, following standard,
you can not pass through the exit) and want it to be direct (USER -> Proxy
-> GW -> CARRIER), just past the entrance.
Anyone could advise me where I could find more information to set up this
scenario?. thanks and sorry for bothering you with this question ;-).
best regards
I can't seem to get kamailio to "*make*". I am following the directions on
the wiki on how to install. I have downloaded, compiled, and installed mysql
server and every time I run to "*make all*" with kamailio, I get this error
message.
At first, I was thinking that *km_db_mysql.c* couldn't find the file. The
header seems to be looking for *mysql.h* (at *#include <mysql/mysql.h>*). I
found the file from installing mysql server and I thought I'd help *
km_db_mysql.c* to find the file, but it still gives me this error.
I am using a power pc running OS X.5.1.
CC (gcc) [M db_mysql.so] km_db_mysql.o
km_db_mysql.c:49:19: error: mysql/mysql.h: No such file or directory
km_db_mysql.c: In function ‘kam_mysql_mod_init’:
km_db_mysql.c:92: warning: implicit declaration of function
‘mysql_get_client_info’
km_db_mysql.c:92: warning: format ‘%s’ expects type ‘char *’, but argument 7
has type ‘int’
km_db_mysql.c:92: warning: format ‘%s’ expects type ‘char *’, but argument 6
has type ‘int’
make[1]: *** [km_db_mysql.o] Error 1
make: *** [modules] Error 1
Peter Schrock
I'm using Kamailio as dispatcher to a FreeSwitch setup.
Currently it "almost" work. I have 2 extensions connected to my FreeSwitch
via Kamailio. However, I can only send calls one way because Kamailio seems
to change the domain on the extension.
One extension is registered with ID(a)sip.my-domain.com. This I can send calls
to.
The other extension is registered with ID@local-ip. This I cannot send calls
to.
Isn't it possible to have Kamailio register the extension on my FreeSwitch
with @sip.my-domain.com?
If I register both extension directly to my FreeSwitch everything works.
Hello,
been trying to run two sip-router proxies in parallel and to feed data
from them to snmpd via agentx. But it looks like snmpd deamon directly
routes snmp request just to one (probably first connected) proxy. What
ways this can be solved? Currenly i am thinking like running two
concurrent snmpd daemons binded to specific IP addresses. Is there a
better way to do it?
best regards,
--
Antanas Masevicius