I am doing a "make all" and am getting this error:
error: mysql/mysql.h: No such file or directory
I have mysql installed and know that kamailio is having trouble finding
mysql header files. Is there a configuration I can set up to help kamailio
find it? Is there a resource I can be directed to find the info?
Peter
Hello,
tomorrow is the day to release the new major version 3.2.0. Since
involves creation of a new branch on GIT repository and some adjustments
to the packaging, the plan is to start in the morning with the
preparations. If any developer has something left to commit, please do
it before 9:00am GMT.
Afterwards it is very likely that the branch 3.2 will be created and
there will be need for backport (which is fine as well). Then by 14:00
GMT the 3.2 branch should be frozen completely to start packaging the
release. From than moment on until the release is announced, please send
an email to sr-dev in case anyone wants to commit to branch 3.2.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello all,
Is there a way to set Organization: within SIP header? I know how to
change user_agent_header and server_header but I'd rather not do that.
Also I know I could do append_hf, but is there an organization_header?
Thanks,
Skyler
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
Hi,
I am seeing several Contacts for same AOR in userlocation when I do "kamctl
ul show". I suspect,
it's a result of UA crashing after registering and then registering with
different contact after restart.
Since the UA crashed, it could not send Register with expire=0 to remove the
previous contact.
Since the userlocation API is not exported to configuration scripting, I am
wondering how to clean any spurious
contacts.
Thanks
Krish Kura
I tried opening with "kamctl moni" and I get this error message:
ERROR: Error opening Kamailio's FIFO FIFO
ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name",
"FIFO")' in your config
ERROR: and also have loaded the mi_fifo module.
I looked at the cfg file and it looks like what it is asking for is already
there. Any suggestions would be welcomed.
Peter
Hi All,
Our system has two IP address, one is used for kamailio and 2nd one is used
for data.
The problem is suppose a request came in to kamailio on a TCP connection
with first IP address and connection is torned down before sending the
response. Later when the response is send out kamialio is using the 2nd IP
to create the connection. The reason is kamailio doesn't have force socket
in in reply, so it uses INADDR_ANY for soruce addres .so kernel uses source
address based on the detaintion IP.
I tired to force the socket using pseudo variable $fs or
force_send_socket(), but neither of them worked from reply_route.
So i modfied the code relay_replay to set the SND_F_FORCE_SOCKET which will
use the address where request is recieved as source address to make the TCP
connection The code change is shown below.
Please let me know is there anyother way we could acheive it?
}else{
buf = build_res_buf_from_sip_res( relayed_msg, &res_len );
/* if we build a message from shmem, we need to remove
via delete lumps which are now stirred in the shmem-ed
structure
*/
if (branch!=relay) {
free_via_clen_lump(&relayed_msg->add_rm);
}
/* update send_flags with possible additions from the
reply route */
SND_FLAGS_OR(&uas_rb->dst.send_flags, &uas_rb->dst.send_flags,
&relayed_msg->rpl_send_flags);
/* Make the response to use the same IP where it receives
the message */
* *
* uas_rb->dst.send_flags.f |= SND_F_FORCE_SOCKET; *
}
Thanks
JIjo
Hi,
I am trying to connect to the iptel.org SIP server using the
recommended jitsi SIP UA.
Is the service still up and running?
I am using my newly created username and password but I get no
response back from the REGISTER I send.
Enda
If the SIP UA is not behind the NAT, and Kamailio insersts a=nortpproxy:yes
in SDP body, can it cause one sided audio.
I am using PJSIP as my UA, kamailio 3.1.5 , rtp proxy 1.2.1 as intermediate
proxy for signalling and media. In kamailio config, I have enabled WITH_NAT.
On call setup, only one way audio is there. When I looked at SIP messages,
the only additional stuff I can see a=nortpproxy and nat=yes in recpord
route.
Without kamailio as intermediate proxy, audio is good both way.
So I feel, when I bring up kamailio as intermediate proxy I am doing some
mistake configuration wise either at PJSIP UA or in Kamailio.
Has anybody faced this issue previously.
If so please share how can we fix this issue.
Thanks in advance
Austin
