Re: [SR-Users] get_profile_size() function help (Alex Balashov)
upgraded,problem solved thank you 2011/2/23 Daniel-Constantin Mierla mico...@gmail.com: What is the version of kamailio used here? I did a fix for this function when it takes three parameters sometime by end of last year, so if you are not using the latest version, just upgrade to it and see if the issue still persists. Cheers, Daniel On 2/22/11 6:38 PM, Henning Westerholt wrote: On Tuesday 22 February 2011, 侯旭光 wrote: On 02/21/2011 04:50 AM, ??? wrote: ALTER:core [main.c 722] : child process 29651 exited by sinal 11 ALTER:core [main.c 725] : core was generated INFO :core [main.c 737] : terminating due to SIGCHILD This is a crash. It's a bug. Then how to get the number of dialogs belonging to a profile? Hi 侯旭光, well, the server should return the number of dialogs here - that it crashs its not normal, of course. :-) Can you take a look to the core dump that was generated and post the result here on the list? More informations can be find here: http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:corefiles Cheers, Henning ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] 422 Session timer too small
Hi, I see in my cdrtool rarely 422 Session Timer too small - the reason why the call was not initiated. Do you have some suggestion how to fix this ? Maybe SST module ? What is the default value of this timer, so that I could increase it ? kamailio 3.1.0 (i386/linux) 1e204f Thank you, Mino ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 422 Session timer too small
Overview through the RFC 4028- Session Timers in the Session Initiation Protocol (SIP) Session-Expires, which conveys the lifetime of the session, and Min-SE, which conveys the minimum allowed value for the session timer. Session-Expires Header Field Definition The Session-Expires header field conveys the session interval for a SIP session. It is placed only in INVITE or UPDATE requests, as well as in any 2xx response to an INVITE or UPDATE. Like the SIP Expires header field, it contains a delta-time. The absolute minimum for the Session-Expires header field is 90 seconds. This value represents a bit more than twice the duration that a SIP transaction can take in the event of a timeout. This allows sufficient time for a UA to attempt a refresh at the halfpoint of the session interval, and for that transaction to complete normally before the session expires. However, 1800 seconds (30 minutes) is RECOMMENDED as the value for the Session-Expires header field. In other words, SIP entities MUST be prepared to handle Session-Expires header field values of any duration greater than 90 seconds, but entities that insert the Session-Expires header field SHOULD NOT choose values of less than 30 minutes. 422 Response Code Definition This extension introduces the 422 (Session Interval Too Small) response code. It is generated by a UAS or proxy when a request contains a Session-Expires header field with a duration below the minimum timer for the server. The 422 response MUST contain a Min-SE header field with the minimum timer for that server. -- Marco Mouta On Wed, Feb 23, 2011 at 2:00 PM, Mino Haluz mino.ha...@gmail.com wrote: Hi, I see in my cdrtool rarely 422 Session Timer too small - the reason why the call was not initiated. Do you have some suggestion how to fix this ? Maybe SST module ? What is the default value of this timer, so that I could increase it ? kamailio 3.1.0 (i386/linux) 1e204f Thank you, Mino ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] pipelimit db schema
Cool, thanks.
On Wed, Feb 23, 2011 at 12:36 AM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
Hello,
On 2/23/11 12:30 AM, thrillerbee wrote:
Can anyone point me to the db schema for the new pipelimit module?
seems I forgot to add it to db creation script. I will fix that in the next
days. Meanwhile you can use:
INSERT INTO version (table_name, table_version) values ('pl_pipes','1');
CREATE TABLE pl_pipes (
id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL,
pipeid VARCHAR(64) DEFAULT '' NOT NULL,
algorithm VARCHAR(32) DEFAULT '' NOT NULL,
plimit INT DEFAULT 0 NOT NULL,
CONSTRAINT pipeid_idx UNIQUE (pipeid)
) ENGINE=MyISAM;
This is inside sources, modules/pipelimit/pl_db.c
Thanks, Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 3.1: forward(10.0.0.10:5060) not working?
Hi
thanks. it works, the script can start without error. ( i did not check
if the msg is really forwarded or not at this time)
yes, the wiki has the old prototypes.
http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#forward
I updated it, please check if it is correct.
Kind regards.
Min
On 02/22/2011 04:45 PM, Daniel-Constantin Mierla wrote:
Hello,
after integration of the new core between Kamailio and SER this
function changed and I guess the wiki is still having the old prototype.
Try:
forward(67.154.xx.xx, 5080);
and see if this one works for you.
Cheers,
Daniel
On 2/22/11 7:30 PM, Min Wang wrote:
HI
It seems the forward(host:port) not working in the kamailio 3.1?
the simple route like:
route {
forward(67.154.xx.xx:5080);
}
the error is: core [proxy.c:278]: ERROR: mk_proxy: could not
resolve hostname: 67.154.xx.xx:5080
Anything missing?
the detailed log is:
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
load_tm in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_newtran in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_relay_to_tcp in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_relay_to_udp in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_relay in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_forward_nonack in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [sr_module.c:625]: find_export_record: found
t_release in module tm [/usr/lib/kamailio/modules/tm.so]
0(8500) DEBUG: core [main.c:2371]: Expect (at least) 18 SER
processes in your process list
0(8500) DEBUG: core [proxy.c:278]: DEBUG: mk_proxy: doing DNS
lookup...
0(8500) DEBUG: core [dns_cache.c:567]:
dns_hash_find(_sip._udp.67.154.xx.xx:5080(28), 33), h=780
0(8500) DEBUG: core [resolve.c:727]: get_record:
lookup(_sip._udp.67.154.xx.xx.:5080, 33) failed
0(8500) DEBUG: core [dns_cache.c:895]:
dns_cache_mk_bad_entry(_sip._udp.67.154.xx.xx:5080, 33, 60, 1)
0(8500) DEBUG: core [dns_cache.c:828]: dns_cache_add: adding
_sip._udp.67.154.xx.xx:5080(28) 33 (flags=1) at 780
0(8500) DEBUG: core [dns_cache.c:567]:
dns_hash_find(67.154.xx.xx:5080(18), 1), h=16
0(8500) DEBUG: core [resolve.c:727]: get_record:
lookup(67.154.xx.xx:5080, 1) failed
0(8500) DEBUG: core [dns_cache.c:895]:
dns_cache_mk_bad_entry(67.154.xx.xx:5080, 1, 60, 1)
0(8500) DEBUG: core [dns_cache.c:828]: dns_cache_add: adding
67.154.xx.xx:5080(18) 1 (flags=1) at 16
0(8500) : core [proxy.c:278]: ERROR: mk_proxy: could not resolve
hostname: 67.154.xx.xx:5080
0(8500) ERROR: core [route.c:1161]: fixing failed (code=-478) at
cfg:/etc/kamailio/kamailio.cfg:394
ERROR: error -478 while trying to fix configuration
0(8500) DEBUG: tm [t_funcs.c:122]: DEBUG: tm_shutdown : start
0(8500) DEBUG: tm [t_funcs.c:125]: DEBUG: tm_shutdown : emptying
hash table
0(8500) DEBUG: tm [t_funcs.c:127]: DEBUG: tm_shutdown : removing
semaphores
0(8500) DEBUG: tm [t_funcs.c:129]: DEBUG: tm_shutdown : destroying
tmcb lists
0(8500) DEBUG: tm [t_funcs.c:132]: DEBUG: tm_shutdown : done
0(8500) DEBUG: core [mem/shm_mem.c:236]: shm_mem_destroy
0(8500) DEBUG: core [mem/shm_mem.c:239]: destroying the shared
memory lock
thx.
--
Kind regards / Mit freundlichen Grüßen
Min Wang
BASIS AUDIONET
North America
BASIS AUDIONET * 716 N. Bethlehem Pike - Suite 300 * Lower Gwynedd * PA 19002 *
USA
Phone +1 215 674 8600 ext 451
Fax+1 215 646 4959
w...@basis-audionet.com
www.basis-audionet.com
Europe
BASIS AUDIONET GmbH * Jessenstraße 4 * 22767 Hamburg * Germany
Phone +49 40 85 31 14-0
Fax+49 40 85 31 14-33
www.basis-audionet.de
Registered: Hamburg HR B 85866
Managing Director: Lutz Schaffhausen, Rüdiger Kaun
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 422 Session timer too small
Am 23.02.2011 15:00, schrieb Mino Haluz: Hi, I see in my cdrtool rarely 422 Session Timer too small - the reason why the call was not initiated. Do you have some suggestion how to fix this ? Maybe SST module ? What is the default value of this timer, so that I could increase it ? kamailio 3.1.0 (i386/linux) 1e204f The call should not fail - you should immediately see another call which works as the client retry with bigger timeout value. You could also configure your gateway to allow smaller timeouts. regards klaus ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Visiting CeBIT 2011 in Hanover (Carsten Bock)
Daniel, I will be there on Thursday/Friday. Cheers. DanB ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] pipelimit db schema
Is there a fifo command available to reload pipelimit config from db?
something like 'kamctl fifo pl_reload'?
On Wed, Feb 23, 2011 at 9:02 AM, thrillerbee thriller...@gmail.com wrote:
Cool, thanks.
On Wed, Feb 23, 2011 at 12:36 AM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
Hello,
On 2/23/11 12:30 AM, thrillerbee wrote:
Can anyone point me to the db schema for the new pipelimit module?
seems I forgot to add it to db creation script. I will fix that in the
next days. Meanwhile you can use:
INSERT INTO version (table_name, table_version) values ('pl_pipes','1');
CREATE TABLE pl_pipes (
id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL,
pipeid VARCHAR(64) DEFAULT '' NOT NULL,
algorithm VARCHAR(32) DEFAULT '' NOT NULL,
plimit INT DEFAULT 0 NOT NULL,
CONSTRAINT pipeid_idx UNIQUE (pipeid)
) ENGINE=MyISAM;
This is inside sources, modules/pipelimit/pl_db.c
Thanks, Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] stats in kamailio
Hello. I’m trying to get statistics to use charts in SIREMIS v2.0. I was able to load the “Memory” statistics but I want to know if there is more information to use from Kamailio, right now I have : $stat(used_size) $stat(real_used_size) $stat(max_used_size) $stat(free_size) $stat(location-users) $stat(location-contacts) Where can I find the complete list of statistics to get from kamailio?. Thanks in advance. Ricardo Martinez.- ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] stats in kamailio
Each module may or may not have statistics. Check the README file for each module that you have loaded to see what statistics are available. For example, here are the statistics exported by the tmx module: http://www.kamailio.org/docs/modules/3.1.x/modules_k/tmx.html#id2700650 Regards, Ovidiu Sas On Wed, Feb 23, 2011 at 2:49 PM, Ricardo Martinez rmarti...@redvoiss.net wrote: Hello. I’m trying to get statistics to use charts in SIREMIS v2.0. I was able to load the “Memory” statistics but I want to know if there is more information to use from Kamailio, right now I have : $stat(used_size) $stat(real_used_size) $stat(max_used_size) $stat(free_size) $stat(location-users) $stat(location-contacts) Where can I find the complete list of statistics to get from kamailio?. Thanks in advance. Ricardo Martinez.- ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] stats in kamailio
Thanks Ovidiu. In particular is there a way to see the statistics related to the load of the server? Or cpu used by kamailio? Thanks Ricardo.- -Mensaje original- De: sip.n...@gmail.com [mailto:sip.n...@gmail.com] En nombre de Ovidiu Sas Enviado el: miércoles, 23 de febrero de 2011 16:52 Para: Ricardo Martinez CC: sr-users@lists.sip-router.org Asunto: Re: [SR-Users] stats in kamailio Each module may or may not have statistics. Check the README file for each module that you have loaded to see what statistics are available. For example, here are the statistics exported by the tmx module: http://www.kamailio.org/docs/modules/3.1.x/modules_k/tmx.html#id2700650 Regards, Ovidiu Sas On Wed, Feb 23, 2011 at 2:49 PM, Ricardo Martinez rmarti...@redvoiss.net wrote: Hello. I’m trying to get statistics to use charts in SIREMIS v2.0. I was able to load the “Memory” statistics but I want to know if there is more information to use from Kamailio, right now I have : $stat(used_size) $stat(real_used_size) $stat(max_used_size) $stat(free_size) $stat(location-users) $stat(location-contacts) Where can I find the complete list of statistics to get from kamailio?. Thanks in advance. Ricardo Martinez.- ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] stats in kamailio
Ricardo asked: In particular is there a way to see the statistics related to the load of the server? Or cpu used by kamailio? Hi, kamctl fifo get_statistics all will show you all available statistics, for a more simpler view try kamctl moni. The closest thing you'll find regards to the load are inuse transaction, or concurrent dialogs. The CPU used from kamailio can be seen by normal system tools like top. Regards, Henning ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] how to forward on busy
Is there an example somewhere that shows how to do forward-on-busy, starting with the kamailio.cfg from version 3.1? Ultimately, I want to use a per-user AVP to obtain the forwarding URI, but just an example that shows how to forward to a fixed URI from the failure route would be great. -- Mark Sidell Partner Forte, Inc. 919-942-7068 fax 919-969-2844 www.forteinc.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] pipelimit db schema
I found the answer to my most recent question (my timer interval was set too
long). Can someone answer this one?
Is there a fifo command available to reload pipelimit config from db?
something like 'kamctl fifo pl_reload'?
On Wed, Feb 23, 2011 at 2:00 PM, thrillerbee thriller...@gmail.com wrote:
...and while I'm asking questions, how should the algorithm be specified in
the db column? Could someone provide some examples?
I'm catching the CPS, but nothing is actually being dropped:
#kamctl fifo pl_get_pipes
PIPE:: id=30236 algorithm=TAILDROP limit=15 counter=82
Thanks.
On Wed, Feb 23, 2011 at 1:32 PM, thrillerbee thriller...@gmail.comwrote:
Is there a fifo command available to reload pipelimit config from db?
something like 'kamctl fifo pl_reload'?
On Wed, Feb 23, 2011 at 9:02 AM, thrillerbee thriller...@gmail.comwrote:
Cool, thanks.
On Wed, Feb 23, 2011 at 12:36 AM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
Hello,
On 2/23/11 12:30 AM, thrillerbee wrote:
Can anyone point me to the db schema for the new pipelimit module?
seems I forgot to add it to db creation script. I will fix that in the
next days. Meanwhile you can use:
INSERT INTO version (table_name, table_version) values ('pl_pipes','1');
CREATE TABLE pl_pipes (
id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL,
pipeid VARCHAR(64) DEFAULT '' NOT NULL,
algorithm VARCHAR(32) DEFAULT '' NOT NULL,
plimit INT DEFAULT 0 NOT NULL,
CONSTRAINT pipeid_idx UNIQUE (pipeid)
) ENGINE=MyISAM;
This is inside sources, modules/pipelimit/pl_db.c
Thanks, Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Lcr Command Disabled
Lcr is working fine but Why would i get LCR commands disabled ? kamctl lcr reload ERROR: command disabled-- Thank You Amit Nepal Systems Administrator Phoenix Internet Phone: 602-385-0731 602-234-0917#112 http://www.phoenixinternet.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] 403 Not Relaying problem
Dear Friends,
With Kamailio 3.1.2, after successfully registering, the caller sends INVITE to
the proxy, and is always responded with 403 not relaying.
I found that in the route[AUTH] subroutine, like below. Regarding the red
comparing, it failed. I also check the code, and found Kamailio will use the
host name in the From header to compare all the socket's IP address, such as
host = mysipserver.com, but socket's ip = 127.0.0.1 or 10.1.1.5. As you can
see, this comparing will never be equal.Could anyone show me how to handle this
problem? Thanks a lot!
# authenticate if from local subscriber if (from_uri==myself)
{ if (!proxy_authorize($fd, subscriber)) {
proxy_challenge($fd, 0); exit; } if
(is_method(PUBLISH)) { if ($au!=$tU) {
sl_send_reply(403,Forbidden auth ID); exit;
} } else { if ($au!=$fU) {
sl_send_reply(403,Forbidden auth ID); exit;
} } consume_credentials(); # caller
authenticated } else { # caller is not local subscriber, then
check if it calls # a local destination, otherwise deny,
not an open relay here if (!uri==myself) {
sl_send_reply(403,Not relaying); exit; } }
Best Regards,Spencer
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
