sr-dev January 2010

sr-dev@lists.kamailio.org

28 participants
289 discussions

Proxy caching patch
by marius zbihlei 26 Jan '10

26 Jan '10

Hello, I have worked lately on the patch that tries to mitigate one performance problem in core:action.c file. I am talking about the multiple calls to mk_proxy(), and the creation of temporary proxies for each FORWARD_T action that the daemon executes. I think this behaviour can be improved by caching certain proxies. My idea is this: * If the next_hop matches a name in the alias list (for example we have an alias for example.com and the next_hop is proxy1.example.com), then cache … [View More]

1 0

[Tracker] Created: (SER-453) harmful stearate and to ree medications can prescription would, https://www.assembla.com/spaces/ultra/documents/dl1fjocGSr34UMeJe5afGb/download/tramadol-sale.html tramadol saturday, >:PP,
by Anonymous (JIRA) 26 Jan '10

26 Jan '10

harmful stearate and to ree medications can prescription would, https://www.assembla.com/spaces/ultra/documents/dl1fjocGSr34UMeJe5afGb/down… tramadol saturday, >:PP, ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SER-453 URL: http://tracker.iptel.org/browse/SER-453 Project: SER Issue … [View More]Type: Bug Affects Versions: 2.0 Environment: 64 bit CPU, Debian lenny OS Assigned To: Vaclav Kubart Fix For: 2.0, Ipteldorf When I try to store message in the database I get the following errors in the syslog (There are no messages stored in the database): May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found And here is ser.cfg: xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n"); if (m_store ("0", "")) { xlog("L_INFO", " route[INBOUND]: offline message stored \n"); xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n"); if (!t_reply("202", "Accepted")) { xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n"); sl_reply_error(); } } the error appears in the following place accordin to my logging: May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, )) May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted) May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE> <sip:hulk@voip.rd.touk.pl> Below is the Message transaction sent through SER: U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060 MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. Content-Type: text/plain;charset=UTF-8. Content-Length: 12. Max-Forwards: 70. . test message # U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089 SIP/2.0 202 Accepted. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05. Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853 req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1". . In the attachment is a patch for the msilo.c source file where there was a need for two small corrections. Cheers Tomasz Zieleniewski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira [View Less]

1 0

[Tracker] Created: (SER-450) tarch medicationas step tablets though available medicinequestions of when buy and, https://www.assembla.com/spaces/ultra/documents/abduSgcGSr34UMeJe5afGb/download/tramadol-online.html tramadol online, =-((,
by Anonymous (JIRA) 26 Jan '10

26 Jan '10

tarch medicationas step tablets though available medicinequestions of when buy and, https://www.assembla.com/spaces/ultra/documents/abduSgcGSr34UMeJe5afGb/down… tramadol online, =-((, ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SER-450 URL: http://tracker.iptel.org/browse/SER-450 … [View More] Project: SER Issue Type: Bug Affects Versions: 2.0 Environment: 64 bit CPU, Debian lenny OS Assigned To: Vaclav Kubart Fix For: 2.0, Ipteldorf When I try to store message in the database I get the following errors in the syslog (There are no messages stored in the database): May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found And here is ser.cfg: xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n"); if (m_store ("0", "")) { xlog("L_INFO", " route[INBOUND]: offline message stored \n"); xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n"); if (!t_reply("202", "Accepted")) { xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n"); sl_reply_error(); } } the error appears in the following place accordin to my logging: May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, )) May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted) May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE> <sip:hulk@voip.rd.touk.pl> Below is the Message transaction sent through SER: U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060 MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. Content-Type: text/plain;charset=UTF-8. Content-Length: 12. Max-Forwards: 70. . test message # U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089 SIP/2.0 202 Accepted. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05. Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853 req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1". . In the attachment is a patch for the msilo.c source file where there was a need for two small corrections. Cheers Tomasz Zieleniewski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira [View Less]

1 0

[Tracker] Created: (SER-448) ut glycolate operative our Therefore pain indicate number, https://www.assembla.com/spaces/ultra/documents/c_kfe6cGSr37EneJe5aVNr/download/tramadol-rx.html tramadol recall, 8987,
by Anonymous (JIRA) 26 Jan '10

26 Jan '10

ut glycolate operative our Therefore pain indicate number, https://www.assembla.com/spaces/ultra/documents/c_kfe6cGSr37EneJe5aVNr/down… tramadol recall, 8987, -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SER-448 URL: http://tracker.iptel.org/browse/SER-448 Project: SER Issue Type: Bug … [View More]Affects Versions: 2.0 Environment: 64 bit CPU, Debian lenny OS Assigned To: Vaclav Kubart Fix For: 2.0, Ipteldorf When I try to store message in the database I get the following errors in the syslog (There are no messages stored in the database): May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found And here is ser.cfg: xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n"); if (m_store ("0", "")) { xlog("L_INFO", " route[INBOUND]: offline message stored \n"); xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n"); if (!t_reply("202", "Accepted")) { xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n"); sl_reply_error(); } } the error appears in the following place accordin to my logging: May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, )) May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted) May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE> <sip:hulk@voip.rd.touk.pl> Below is the Message transaction sent through SER: U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060 MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. Content-Type: text/plain;charset=UTF-8. Content-Length: 12. Max-Forwards: 70. . test message # U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089 SIP/2.0 202 Accepted. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05. Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853 req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1". . In the attachment is a patch for the msilo.c source file where there was a need for two small corrections. Cheers Tomasz Zieleniewski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira [View Less]

1 0

[Tracker] Created: (SER-449) credit that ffffff and prevent using boards be Ultracet tumours, https://www.assembla.com/spaces/ultra/documents/b8AI2IcGKr34XKeJe5aVNr/download/tramadol-180.html tramadol 180, 04550,
by Anonymous (JIRA) 26 Jan '10

26 Jan '10

credit that ffffff and prevent using boards be Ultracet tumours, https://www.assembla.com/spaces/ultra/documents/b8AI2IcGKr34XKeJe5aVNr/down… tramadol 180, 04550, ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: SER-449 URL: http://tracker.iptel.org/browse/SER-449 Project: SER Issue Type: Bug … [View More] Affects Versions: 2.0 Environment: 64 bit CPU, Debian lenny OS Assigned To: Vaclav Kubart Fix For: 2.0, Ipteldorf When I try to store message in the database I get the following errors in the syslog (There are no messages stored in the database): May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found And here is ser.cfg: xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n"); if (m_store ("0", "")) { xlog("L_INFO", " route[INBOUND]: offline message stored \n"); xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n"); if (!t_reply("202", "Accepted")) { xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n"); sl_reply_error(); } } the error appears in the following place accordin to my logging: May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, )) May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted) May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE> <sip:hulk@voip.rd.touk.pl> Below is the Message transaction sent through SER: U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060 MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. Content-Type: text/plain;charset=UTF-8. Content-Length: 12. Max-Forwards: 70. . test message # U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089 SIP/2.0 202 Accepted. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05. Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853 req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1". . In the attachment is a patch for the msilo.c source file where there was a need for two small corrections. Cheers Tomasz Zieleniewski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira [View Less]

1 0

Questions about the command : serctl fifo
by inge 26 Jan '10

26 Jan '10

Hi, I am using SER 0.9.9. I have questions about two commands : - serctl fifo t_stats : What does mean the "current", "waiting" and "total" values returned by the command? - serctl fifo ul_stats : What does mean the two values returned on the line "location"? Regards, David.

2 1

git:master: app_lua: run Lua scripts from cfg
by Daniel-Constantin Mierla 25 Jan '10

25 Jan '10

Module: sip-router Branch: master Commit: 7b91c4d48ecc3b2da82b21966c9fb75fa392f3e5 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7b91c4d… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Tue Jan 26 00:11:02 2010 +0100 app_lua: run Lua scripts from cfg - new module to run embedded Lua scripts from cfg - module exports functions to Lua in order to access current processed SIP … [View More]

1 0

current running action
by Andreea Ancuta Onofrei 25 Jan '10

25 Jan '10

Dear all, Is it possible to retrieve the current action that sip-router is running? Best regards, Ancuta

3 3

git:kamailio_3.0: drouting(k): Makefile updated to link libs
by Daniel-Constantin Mierla 25 Jan '10

25 Jan '10

Module: sip-router Branch: kamailio_3.0 Commit: f572564e862a56470ccb2bc2aa2b23fcbb5dd318 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f572564… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Jan 25 10:06:41 2010 +0100 drouting(k): Makefile updated to link libs - fixed missing core libs in Makefile - reported by Denis Pulyato --- modules_k/drouting/Makefile | 5 +++++ … [View More]

1 0

git:tmp/pipelimit: pipelimit: module for pipe traffic limit
by Daniel-Constantin Mierla 24 Jan '10

24 Jan '10

Module: sip-router Branch: tmp/pipelimit Commit: 163cd084ab97d8938dd014867f70811f0cffa54f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=163cd08… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Sun Jan 24 22:25:03 2010 +0100 pipelimit: module for pipe traffic limit - based on ratelimit - has only pipe functionality so far - pipe definitions loaded from database - pipe id is name -… [View More]

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
29
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2010