sr-users April 2012

sr-users@lists.kamailio.org

75 participants
132 discussions

Re: [SR-Users] CallControl and MediaProxy

by Daniel-Constantin Mierla

Hello, I will patch and backport during next days -- I was mostly out of the office during past weeks. Cheers, Daniel On 3/12/12 11:30 AM, Reda Aouad wrote: > Hi Daniel, > > Any plans to backport this to 3.2 ? > I could still do the changes manually before compilation if you don't > have time to do it. > > Thank you again > Reda > > > > On Wed, Feb 29, 2012 at 10:19, Reda Aouad <reda.aouad(a)gmail.com > <mailto:reda.aouad@gmail.com>> wrote: > > Daniel, It works with flag 28. > Can you confirm that flag 28 isn't used by another module? > If so, can you patch it? When is the next release scheduled for? > > The following are the changes I made: > > modules_k/call_control.c: flag changed to 28 > ------------------------------------------- > #define FL_USE_CALL_CONTROL (1<<28) // use call control for > a dialog > > parser/msg_parser.h: warning added > ------------------------------------------- > /* WARNING: Value (1 << 28) is temporarily reserved for use in > kamailio call_control > * module (flag FL_USE_CALL_CONTROL )! */ > > > Thank you :) > Reda > > > > On Wed, Feb 29, 2012 at 09:58, Reda Aouad <reda.aouad(a)gmail.com > <mailto:reda.aouad@gmail.com>> wrote: > > A quick grep on flags FL_* in the sources shows the following : > Flag 29 is used by acc module, 31 by nat_traversal, 0 to 12 in > the parser. > Thus I assume that it is safe to test using flag 28. > I'll keep you posted on the test result. > > You'll also find below warnings in msg_parser.h for the used > flags. Since flag 30 is declared for mediaproxy in > msg_parser.h, I'll change the flag of callcontrol to 28. > > ----------------------------------------------------------------- > /* WARNING: Value (1 << 29) is temporarily reserved for use in > kamailio acc > * module (flag FL_REQ_UPSTREAM)! */ > > /* WARNING: Value (1 << 30) is temporarily reserved for use in > kamailio > * media proxy module (flag FL_USE_MEDIA_PROXY)! */ > > /* WARNING: Value (1 << 31) is temporarily reserved for use in > kamailio > * nat_traversal module (flag FL_DO_KEEPALIVE)! */ > ----------------------------------------------------------------- > > $ grep -R 'define FL.* (1' src/kamailio/kamailio-3.2.0 > > modules_k/call_control/call_control.c:#define > FL_USE_CALL_CONTROL (1<<30) // use call control for a dialog > modules_k/nat_traversal/nat_traversal.c:#define > FL_DO_KEEPALIVE (1<<31) > modules_k/acc/acc.h:#define FL_REQ_UPSTREAM (1<<29) > parser/msg_parser.h:#define FL_FORCE_RPORT (1 << 0) /*!< force > rport */ > parser/msg_parser.h:#define FL_FORCE_ACTIVE (1 << 1) /*!< > force active SDP */ > parser/msg_parser.h:#define FL_SDP_IP_AFS (1 << 2) /*!< SDP > IP rewritten */ > parser/msg_parser.h:#define FL_SDP_PORT_AFS (1 << 3) /*!< SDP > port rewritten */ > parser/msg_parser.h:#define FL_SHM_CLONE (1 << 4) /*!< msg > cloned in SHM as a single chunk */ > parser/msg_parser.h:#define FL_TIMEOUT (1 << 5) /*!< > message belongs to an "expired" branch > parser/msg_parser.h:#define FL_REPLIED (1 << 6) /*!< > message branch received at least one reply > parser/msg_parser.h:#define FL_HASH_INDEX (1 << 7) /*!< > msg->hash_index contains a valid value (tm use)*/ > parser/msg_parser.h:#define FL_MTU_TCP_FB (1 << 8) > parser/msg_parser.h:#define FL_MTU_TLS_FB (1 << 9) > parser/msg_parser.h:#define FL_MTU_SCTP_FB (1 << 10) > parser/msg_parser.h:#define FL_ADD_LOCAL_RPORT (1 << 11) /*!< > add 'rport' to local via hdr */ > parser/msg_parser.h:#define FL_SDP_BODY (1 << 12) /*!< > msg has SDP in body */ > modules/mediaproxy/mediaproxy.c:#define FL_USE_MEDIA_PROXY (1<<30) > > ----------------------------------------------------------------- > > > Reda > > > > On Wed, Feb 29, 2012 at 00:18, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > That should be. Try changing one of them to (1<<29) and > see if all works fine. > > On another hand, defining and using core msg flags in a > module is a risk, a different solution has to be done, a > simple one is to move the definition of these flags in the > core, so there will be no overlap in the future. > > Cheers, > Daniel > > > On 2/27/12 9:32 PM, Reda Aouad wrote: >> I looked into mediaproxy.c and found the following : >> >> ------------------------------------------------------- >> #define FL_USE_MEDIA_PROXY (1<<30) >> >> ... >> >> # dialog callback >> >> __dialog_created (...) { >> .... >> if ((request->msg_flags & FL_USE_MEDIA_PROXY) == 0) >> return; >> .... >> use_media_proxy (...); >> } >> ------------------------------------------------------- >> >> >> I also found this in call_control.c >> ------------------------------------------------------- >> #define FL_USE_CALL_CONTROL (1<<30) >> >> # Public API >> CallControl (...) { >> ... >> msg->msg_flags |= FL_USE_CALL_CONTROL; >> ... >> } >> ------------------------------------------------------- >> >> So I suspect that since the call_control module uses the >> same flag as the mediaproxy module, call_control function >> is used, flag 30 is set, and the following condition in >> the __dialog_created callback function above is never met >> >> (request->msg_flags & FL_USE_MEDIA_PROXY) == 0 >> >> so the callback function continues until executing its >> last line : use_media_proxy (...) >> which is called on every call to call_control ( ) function.. >> >> Reda >> >> >> >> On Mon, Feb 27, 2012 at 18:39, Reda Aouad >> <reda.aouad(a)gmail.com <mailto:reda.aouad@gmail.com>> wrote: >> >> Ok thanks Daniel. >> >> I'll do what you suggested and we'll see how to proceed. >> >> Thanks again >> Reda >> > > > -- > Daniel-Constantin Mierla --http://www.asipto.com > http://linkedin.com/in/miconda -- http://twitter.com/miconda > > > > -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/

12 years, 3 months

SIP Status: 401 Unauthorized (0 bindings)

by Saul Waizer

Hello List, I have a fresh install kamailio 3.2.0 running on ubuntu. Everything seems to work fine according to the logs, I have enabled support for the following: - enabled support to connect to MySQL server - enabled user authentication - enabled persistent user location service - enabled NAT traversal and updated RTPProxy control socket parameter I added a few users with kamctl add user pass but when I try to register with my client I get the following: 8.257745 x.x.x.x -> 10.62.99.103 SIP Request: REGISTER sip:x.x.x.x 8.258462 10.62.99.103 -> x.x.x.x SIP Status: 401 Unauthorized (0 bindings) Here are some detailed logs for the reg process: T x.x.x.x:63171 -> 10.62.99.103:5060 [AP] REGISTER sip:x.x.x.x SIP/2.0. Via: SIP/2.0/TCP 192.168.126.19:4369;rport;branch=z9hG4bK239028812. From: <sip:daniel@x.x.x.x>;tag=303867081. To: <sip:daniel@x.x.x.x>. Call-ID: 1300614569. CSeq: 7 REGISTER. Contact: <sip:daniel@x.x.x.x:63171;transport=tcp;line=5a9552052fb65c8>. Max-Forwards: 70. User-Agent: Linphone/3.5.0 (eXosip2/3.6.0). Expires: 600. Content-Length: 0. . T 10.62.99.103:5060 -> x.x.x.x:63171 [AP] SIP/2.0 401 Unauthorized. Via: SIP/2.0/TCP 192.168.126.19:4369 ;rport=63171;branch=z9hG4bK239028812;received=x.x.x.x. From: <sip:daniel@x.x.x.x>;tag=303867081. To: <sip:daniel@x.x.x.x>;tag=b27e1a1d33761e85846fc98f5f3a7e58.b260. Call-ID: 1300614569. CSeq: 7 REGISTER. WWW-Authenticate: Digest realm="x.x.x.x", nonce="T42z9U+NssnZP82+sdkwPgl1nRk61QDm". Server: kamailio (3.2.0 (i386/linux)). Content-Length: 0. Any help is greatly appreciated.

12 years, 3 months

How to configure Kamailio routing logic based on mobile phone numbers

by Tam Doan

Hi there, Now I could configure Kamailio routing logic based on service's short code (i.e route calls to 200, 300 to separated service's appliction (so call, app serv 1 and app serv 2). My problem is how can i configure Kamailio so that it can route the call from mobile numbers, such as calls from mobile number starting with 0988 xxxxx, 0978 xxxxx will be routed to app serv1 and the calls of 0976 xxxxx to app serv 2. So do you guys have an answer for me ? I would really appreciate your help!!!

12 years, 3 months

registrar/usrloc updates - gruu support (rfc 5627)

by Daniel-Constantin Mierla

Hello, I just pushed GRUU support in git master branch. That implied adding two new columns to location table, therefore if you use devel version, **you have to update your db schema**. Perhaps a bit of tuning will follow in the next days, but GRUU support should be fully functional in terms of routing. Testing and feedback will be very appreciated as well as hints on what SIP hard/phones support GRUU properly. Be also aware that now you may have to do lookup location even for within dialog requests, if the r-uri is a local GRUU. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany http://www.asipto.com/index.php/kamailio-advanced-training/

12 years, 3 months

dispatcher didnt use the gateway

by Karsten Horsmann

Hi List! I try to use the dispatcher module to route calls to my ivr systems. But it didnt load the gateway. I didnt see my xlog message after the ds_select_dst() Any hints? Gateway is Active and Probing. #!ifdef WITH_DISPATCHER if (!lookup("location")) { if(ds_select_dst("1", "4")) xlog("DISPATCHER ds_select_dst\n"); #forward(); } #!endif [root@kamailio1 log]# kamctl fifo ds_list SET_NO:: 1 SET:: 1 URI:: sip:172.20.100.61:5060 flags=AP priority=0 attrs= -- Mit freundlichen Grüßen *Karsten Horsmann*

12 years, 3 months

PDD Timer (Branch Level)

by Orlando F. Guitian

Recently, I have used TM's fr_timer() parameter to control PDD, non-responsive gateways, etc. However, I would like to know if it is possible to set the fr_timer(), or something similar, on a per branch level. For example, in comparison to our US-based gateways, some of our international gateways may require a higher PDD value. Is it possible to assign a branch-specific timeout value? Thank you, Orlando -- Orlando F. Guitian OrlandoG(a)gmail.com <OrlandoG(a)gmail.com>www.AsteriskCertified.com<http://www.asteriskcertified.com/>

12 years, 3 months

kamctl ps in 1.5.0 equivallent in 3.1.2

by Renan Capaverde

Hello list, In kamailio 1.5.0 there is one command called 'ps'. Which when executed produces an output similar to: Process:: ID=0 PID=29533 Type=attendant Process:: ID=1 PID=29537 Type=SIP receiver udp:192.168.166.75:5060 Process:: ID=2 PID=29538 Type=SIP receiver udp:192.168.166.75:5060 Process:: ID=3 PID=29539 Type=SIP receiver udp:192.168.166.75:5060 Process:: ID=4 PID=29540 Type=SIP receiver udp:192.168.166.75:5060 Process:: ID=5 PID=29541 Type=timer Process:: ID=6 PID=29542 Type=timer Process:: ID=7 PID=29543 Type=MI FIFO Process:: ID=8 PID=29544 Type=TCP receiver Process:: ID=9 PID=29545 Type=TCP receiver Process:: ID=10 PID=29546 Type=TCP receiver Process:: ID=11 PID=29547 Type=TCP receiver Process:: ID=12 PID=29548 Type=TCP main In kamailio 3.1.2, I get the following output: *500 command 'ps' not available *Is there any equivalent for *kamctl ps* in version 3.1.2? Regards, -- *Renan Capaverde* /Estagiário Nível Superior/ /DDT - STE - Soluções em Tecnologia e Embarcados/ *DÍGITRO TECNOLOGIA* *E-mail:* renan.capaverde(a)digitro.com.br <mailto:renan.capaverde@digitro.com.br> *Fone:* +55 48 3281-7000*Ramal:* 8132 *Fax:* +55 48 3281-7299 *Site:* www.digitro.com <http://www.digitro.com> /"Antes de imprimir, pense na sua responsabilidade e no seu compromisso com o meio ambiente"/ Esta mensagem, incluindo seus anexos, é reservada somente à Dígitro e ao destinatário da mensagem. Caso você tenha recebido esta mensagem por engano, queira por favor, retorná-la ao remetente e apagá-la de seus arquivos.

12 years, 3 months

Kamailio and Oracle

by Orlando F. Guitian

Hi. I am attempting to install Kamailio with the DB_ORACLE module, but I am running into an error. Basically, I am running a CentOS 64-bit and I have also installed the instant client SDK and header files (v10.2) from Oracle. However, the installation is erroring out when trying to find the Oracle XE Client directory (v10.2). However, I am unable to find an Oracle 10g XE Client download in 64 bit version. Does anybody have a work around? Or is there another way to install Kamailio with Oracle? Thank you, Orlando -- Orlando F. Guitian OrlandoG(a)gmail.com <OrlandoG(a)gmail.com>www.AsteriskCertified.com<http://www.asteriskcertified.com/>

12 years, 3 months

Failed shared memory allocation even though there's enough free memory

by Alex Hermann

Hello, i'm seeing a lot of failed memory allocations for shared memory after the shared memory has been fully used once (see shmem:max_used_size below). Used_size keeps increasing fast on a heavy loaded server, until it reaches the total_size. From that moment memory allocations start failing and eventually used_size starts dropping. After while, even when there's a lot of free memory, new allocations keep failing. ERROR:tm:build_uac_req: no more share memory (19852) ERROR:tm:t_uac: failed to build message ERROR:presence:send_notify_request: in function tmb.t_request_within ERROR:presence:notify: sending Notify not successful ERROR:presence:publ_notify: Could not send notify for dialog When i request the shmem statistics at such time, there's lots of free memory: shmem:total_size = 268435456 shmem:used_size = 3749696 shmem:real_used_size = 4822288 shmem:max_used_size = 268048584 shmem:free_size = 263613168 shmem:fragments = 62156 This is on 1.5.x, any suggestion on why it keeps failing and how to prevent this error? -- Greetings, Alex Hermann

12 years, 3 months

Question about processing of packet

by Fabian Borot

greetings, I have a customer that is sending the REGISTER with 2 ports in the Contact header: Contact: <sip:44435661000448181@201.xxx.xxx.xxx:19778:5060> After some troubleshooting we found that the wireless router is the one inserting the 2nd port. It is not the SIP UA itself. Is it possible to "sanitize" the REGISTER at the beginning of the configuration logic with the TEXTOPS module so that we can leave one port and then process the REGISTERwith the typical: if (!www_authorize("$fd", "subscriber")){...} Or will this only applies to messages that are proxied/forwarded (example: received malformed INVITE, before calling route[1] to send it to the destination sanitize it with the TEXTOPS functions)I guess my question is: after removing the extra port at the begining, when I call the "if (!www_authorize("$fd", "subscriber"))",will it process the modified version or the original one? txs a lot fborot

12 years, 3 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users April 2012