sr-users October 2008

sr-users@lists.kamailio.org

93 participants
169 discussions

Re: [Kamailio-Users] Interfaceing Presence server with Presence Network Aget(PNA)

by Daniel-Constantin Mierla

please cc to mailing list. Daniel On 10/15/08 07:51, suresh tattikota wrote: > hi Daniel thank u > > > *PNA*:presence network agent , it collects the presence information of > the network element like *HSS*(Home Subscriber Server) and > *S-CSCF*(serving call session control function) (i.e registered are > unregistered ).Using '*sh'* interface i am collecting these > information through *SNR/SNA,PNR/PNA*(subscribe notify request and > answer,,push notify request/answer ) after getting the PNR i have to > send PUBLISH message to the presence server through *PEN*(its nothing > but publish message )interface , > > My question is how to connect the presence server with presence > network agent . > and how to attach the presence information to the PUBLISH XML body . > > thank you very much > > > On 10/14/08, *Daniel-Constantin Mierla* <miconda(a)gmail.com > <mailto:miconda@gmail.com>> wrote: > > Hello, > > On 10/13/08 12:30, suresh tattikota wrote: > > > hi all > > I am trying to develop the interface between PNA and PS,that > is PEN interface, > for that i am using the one openser 1.2 as the PNA > Application server and Presence server. > > it is recommended that you use kamailio 1.4.1 as presence server, > it has many improvements in this area, openser 1.2 is rather old > and not supported anymore > > > I already developed sh interface between HSS and the PNA. > After getting the PNR request from HSS,PNA has to send the > PUBLISH message to PS > > so here my doubt is > > 1.How to connect the PNA and PS > 2.how to construct PUBLISH XML body > 3.can i use the opensips/openser as presence network agent > > The problem with the questions you ask is that you use a lot of > abbreviations from IMS specs (as they look) . You won't find good > answers unless you get to more details of what you want to > achieve, preferably at SIP level - nobody will spend time to > understand what PS, PEN, PNA are supposed to do. > > Kamailio (OpenSER) can be used as: > - presence server - can handle PUBLISH/SUBSCRIBE messages and send > NOTIFYs > - presence user agent - initiate PUBLISH requests > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla > http://www.asipto.com <http://www.asipto.com/> > > -- Daniel-Constantin Mierla http://www.asipto.com

16 years, 1 month

[Kamailio-Users] New OpenXCAP release 1.0.5

by Adrian Georgescu

Hello, There are new releases of the open source OpenXCAP server and a Python XCAP library available. They contain many bug fixes and lessons learnt at SIPIT 23, still in progress in Lannion, France. Changelogs are attached: openxcap (1.0.5) unstable; urgency=low * fixed: openxcap with 'openser' backend could be start if enable_publish_xcapdiff=yes * fixed a couple of potential Internal Server Errors * added python-mysqldb to dependencies * added <entry> node to <uniqueness-failure> error as required by RFC * nicer error messages in several cases openxcap (1.0.4) unstable; urgency=low * Disabled authentication for requests in /global/ context, because it didn't work well. It is safe, because the only use for /global/ now is retrieving xcap-caps. openxcap (1.0.3) unstable; urgency=low * Fixed: requesting XCAP root resulted in 500 (now 404) * Fixed: multiple matches resulted in 500 (now 404) * Improved error responses openxcap (1.0.2) unstable; urgency=high * Fixed and improved logging. it now logs much more then before and can be customized * Fixed bug: xcap-caps application was not available under /global/ tree * Added experimental support for sqlite database * Fixed multiple xcap roots/aliases. having more then one root= entry in the config is legal now * Fixed bug that made OpenXCAP dependent on specific MySQLdb versions (those with 'reconnect' parameter) * Fixed pyxml issue: previously, if pyxml was not installed, OpenXCAP would fail with obscure exception on element operation. Now it refuses to start. * Fixed URI parsing * Better error reporting in many cases * Many more bugs fixes openxcap (1.0.1) unstable; urgency=low * Added proper URI parsing, so att_value may contain slashes now * Fixed schemas not to fetch files from the internet on initialization python-xcaplib (1.0.6) unstable; urgency=low * made "index" default filename for xcapclient as well * made --app unnecessary for all types of requests if -i is present python-xcaplib (1.0.5) unstable; urgency=low * changed default filename from index.xml to index * changed default auth to None (support both basic and digest) * removed loading options from environ (XCAP_ROOT etc) * added -a, --account-name option * added --show-config option python-xcaplib (1.0.4) unstable; urgency=low * added --sip-address option (sip_address in the config file) python-xcaplib (1.0.3) unstable; urgency=low * added support for documents in the global context * added --filename parameter to xcapclient python-xcaplib (1.0.2) unstable; urgency=low * removed setuptools from setup.py completely python-xcaplib (1.0.1) unstable; urgency=low * fixed setup.py to use setuptools only if available How to upgrade or install the software For Debian testing or unstable on an i386 architecture there is an official public repository provided by AG Projects. Install the AG Projects debian software signing key: wget http://download.ag-projects.com/agp-debian-gpg.key apt-key add agp-debian-gpg.key Add these lines in etc/apt/sources.list # AG Projects software deb http://ag-projects.com/debian unstable main deb-src http://ag-projects.com/debian unstable main After that, run: apt-get update apt-get install openxcap python-xcaplib For other operating systems download the tar archive from: http://openxcap.org Kind regards, Adrian Georgescu

16 years, 1 month

Re: [Kamailio-Users] Client REGISTERED but "404-NOT FOUND"

by luzango mfupe

> > Hi Castilo, Yea you might be right that my conclusion is wrong but in my case at least a client must be in the ACL in order to be able to make PSTN calls,unregistered clients cant call as well. I tested the same configuration with a X-lite client and it was possible to make calls. > ...debug why your dialed number is not matched as a number to the PSTN. > > Can you explain here a lil bit more?? because the regex part in my config > is working fine it matches all PSTN[Local & Int.] perfectly!! Cheers, Lu. > > > Message: 2 > Date: Wed, 15 Oct 2008 10:48:48 +0200 > From: " I?aki Baz Castillo " <ibc(a)aliax.net> > Subject: Re: [Kamailio-Users] Client REGISTERED but "404-NOT FOUND" > during INVITE > Cc: users(a)lists.kamailio.org > Message-ID: > <cc1f582e0810150148h1ba9b282t94ae8278c3550e27(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > 2008/10/15 luzango mfupe <luzango.mfupe(a)gmail.com>: > > > > > > Hi Mates, > > I am testing a Client in Nokia E65 using kamailio 1.3.3. I managed to > > successfull get it Registered but when i attempt to make a call i always > get > > the "404 Not Found" message in the INVITE. Strangely enough, the Client > > appears to still be ONLINE in the location table. > > Your conclusion is wrong. A user doen't need to be registered in order > to make a PSTN call (except if you add that logic to your script, that > is not the case). > > So, forget yuor user is registered, it's doesn't matter, and debug why > your dialed number is not matched as a number to the PSTN. > > > -- > I?aki Baz Castillo > <ibc(a)aliax.net> > > ------------------------------ > > _______________________________________________ > Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > > > End of Users Digest, Vol 41, Issue 42 > ************************************* > -- Luzango Mfupe TUUNE MOBILE Tel:0128440528/0123825710 Tshwane-RSA "...Ships are safe in harbor, but they were never meant to stay there......."

16 years, 1 month

[Kamailio-Users] Rouge UAC: location database not updated

by CSB

I see the following messages in the logs: Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:parse_from_header: bad from header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:siptrace:sip_trace: cannot parse FROM header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:get_hdr_field: bad to header Oct 14 15:59:58 beta /sbin/openser[32535]: INFO:core:parse_headers: bad header field Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:maxfwd:is_maxfwd_present: parsing MAX_FORWARD header failed! Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:get_hdr_field: bad to header Oct 14 15:59:58 beta /sbin/openser[32535]: INFO:core:parse_headers: bad header field Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:rr:find_first_route: failed to parse headers Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:parse_from_header: bad from header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:parse_from_uri: cannot parse FROM header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:domain:is_from_local: Error while parsing From header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:get_hdr_field: bad to header Oct 14 15:59:58 beta /sbin/openser[32535]: INFO:core:parse_headers: bad header field Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:get_hdr_field: bad to header Oct 14 15:59:58 beta /sbin/openser[32535]: INFO:core:parse_headers: bad header field Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:build_res_buf_from_sip_req: parse_headers failed Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:sl:sl_send_reply_helper: response building failed Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:get_hdr_field: bad to header Oct 14 15:59:58 beta /sbin/openser[32535]: INFO:core:parse_headers: bad header field Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:pv_get_to_attr: cannot parse To header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:parse_from_header: bad from header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:pv_get_from_attr: cannot parse From header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:parse_from_header: bad from header Oct 14 15:59:58 beta /sbin/openser[32535]: ERROR:core:pv_get_from_attr: cannot parse From header This seems to have been caused by one rogue UAC and has the effect of preventing entries being written to the location database. My question: could anyone suggest how to prevent a UAC which is sending some weird data from causing the server to choke? Thanks Cameron

16 years, 1 month

Re: [Kamailio-Users] problem starting kamailio

by ingdavidcespedes＠cable.net.co

16 years, 1 month

[Kamailio-Users] problem starting kamailio

by Fabian Borot

hello I installed kamailio, and want to use mysql auth,loaded the mysql module, uncomented the lines needed to use mysql in the .cfg file I ran the openser_mysql.sh script, and when I try to started kamailio and this is what I see in the console: [root@sp1094a sbin]# ./openser_mysql.sh create MySql password for root: Domain (realm) for the default user 'admin': 65.111.185.187 creating database openser ... Install SERWEB tables ?(y/n):n # I tried with and w/o the servweb tables [root@sp1094a sbin]# ./kamctl start database engine 'MYSQL' loaded Control engine 'FIFO' loaded INFO: Starting Kamailio : ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed in the var/log/message file this is what I see: Oct 14 21:09:12 sp1094a ./kamailio[29249]: NOTICE:core:main: version: kamailio 1.4.1-notls (i386/linux) Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:core:main: using 32 Mb shared memory Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:core:main: using 1 Mb private memory per process Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:sl:mod_init: Initializing StateLess engine Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:tm:mod_init: TM - initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:maxfwd:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:usrloc:ul_init_locks: locks array size 512 Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:registrar:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:textops:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:xlog:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:acc:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:auth:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:auth_db:mod_init: initializing... Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 210 kb Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:db_mysql:db_mysql_submit_query: driver error on query: Unknown column 'cflags' in 'field list' Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:core:db_do_query: error while submitting query Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:usrloc:preload_udomain: db_query (1) failed Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:usrloc:child_init: child(1): failed to preload domain 'location' Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:core:init_mod_child: failed to initializing module usrloc, rank 1 Oct 14 21:09:12 sp1094a ./kamailio[29253]: ERROR:core:main_loop: init_child failed for UDP listener Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:core:handle_sigs: child process 29253 exited normally, status=255 Oct 14 21:09:12 sp1094a ./kamailio[29249]: INFO:core:handle_sigs: terminating due to SIGCHLD Oct 14 21:09:12 sp1094a ./kamailio[29264]: INFO:core:sig_usr: signal 15 received Oct 14 21:09:12 sp1094a ./kamailio[29261]: INFO:core:sig_usr: signal 15 received Oct 14 21:09:12 sp1094a ./kamailio[29259]: INFO:core:sig_usr: signal 15 received Oct 14 21:09:12 sp1094a ./kamailio[29257]: INFO:core:sig_usr: signal 15 received Oct 14 21:09:12 sp1094a ./kamailio[29255]: INFO:core:sig_usr: signal 15 received what can that be? txs Fabian <html><DIV> <DIV> </DIV></DIV></html> _________________________________________________________________ Get more out of the Web. Learn 10 hidden secrets of Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!5…

16 years, 1 month

Re: [Kamailio-Users] How to handle DoS attack and OpenSER Pike module!

by Daniel-Constantin Mierla

Hello, On 10/14/08 09:32, Arif-Uz-Zaman wrote: > Hi all, > I need to bother about crazy client by considering “Flood” detection > technique. I can do it by using OpenSER Pike > <http://kamailio.org/docs/modules/1.2.x/pike.html> module which helps > to keep trace of all (or selected ones) incoming request's IP source > and blocks the ones that exceeded some limit. > > In my case: If the number of SIP messages from a single IP address to > my SIP Proxy exceeds *200* per minute. Recommended action: Block IP > for 2 hours. > > I tried with the pike module but I’m little bit confused with > sampling, density, and timeout value. > > Please help me with example configuration by considering my point. > have you tried: modparam("pike", "sampling_time_unit", 60) modparam("pike", "reqs_density_per_unit", 200) modparam("pike", "remove_latency", 7200) Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

16 years, 1 month

[Kamailio-Users] Interfaceing Presence server with Presence Network Aget(PNA)

by suresh tattikota

hi all I am trying to develop the interface between PNA and PS,that is PEN interface, for that i am using the one openser 1.2 as the PNA Application server and Presence server. I already developed sh interface between HSS and the PNA. After getting the PNR request from HSS,PNA has to send the PUBLISH message to PS so here my doubt is 1.How to connect the PNA and PS 2.how to construct PUBLISH XML body 3.can i use the opensips/openser as presence network agent thank you regards suresh

16 years, 1 month

Re: [Kamailio-Users] what is the best solution NAT problem

by Ricky Gutierrez

Sunday, October 12, 2008 3:43:16 PM Iñaki Baz Castillo wrote: OpenSer behind a NAT router with dynamic IP? It's really an annoying scenario. Note that when the INVITE/200/(ACK) comes from the LAN 192.168.10.X and goes through OpenSer, you must replace the media IP in the SDP and the IP in "Contact" with the **public** IP of the LAN router, that is a dynamic IP and AFAIK it's not valid to set a domain in the SDP. And when he INVITE/200/(ACK) comes from Internet and goes through OpenSer, you must replace the media IP in the SDP and IP in "Contact" with the eth1 IP of RtpProxy (19.168.10.1). Iñaki I am replacing it for the private ip that I obtain of my router adsl 192.168.1.64, in some examples I read that they replace for the ip it public.. what you try to say is that it replaces the ip that comes from the router for the ip of the lan Also, you need the SIP ports and RtpProxy media ports redirected in the router to the RtpProxy server. that already has it configured in my router ... Anyway, this scenario is not appropiate for a businnes service. you are right, I have a wall of NAT I have open the ports UDP 5060:5065, 10000:20000, 35000:65000 TCP: 5060 Why do you open all these ports? and what do you mean with "open"? don't you mean "redirected"? excuse me, I meant that the ports this redirect to my server PD: A suggestion: Buy an space in a datacenter (a virtual machine could be enough depending on your traffic ammount) and install the OpenSer and RtpProxy decently in a host with public IP. ;) best regards .. rickygm

16 years, 1 month

[Kamailio-Users] presence module, events

by toly

Greetings, This is a question to the author: bogdan_iancu, but if anybody can answer, I'd appreciate it. Softphone client is Bria. Here is publish event from ngrep PUBLISH sip:tolyp@webley SIP/2.0. Via: SIP/2.0/TCP 10.50.1.101:45464;branch=z9hG4bK- T 2008/10/13 16:15:38.621949 10.50.1.101:1572 -> 10.50.4.40:5070 [AP] d8754z-697cf1172b7bf515-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:tolyp@10.50.1.101:1572;transport=TCP>. To: "tolyp"<sip:tolyp@webley>. From: "tolyp"<sip:tolyp@webley>;tag=ca65f37d. Call-ID: YmFlNjUxMzEwM2Q4Nzk0MWRhZGUxZmQwMDA5NmE4Nzc.. CSeq: 1 PUBLISH. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/pidf+xml. User-Agent: Bria release 2.4 stamp 49274. Event: presence. Content-Length: 441. . <?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' xmlns:lt='urn:ietf:params:xml:ns:location-type' entity='sip:tolyp@webley'><tuple id='t5a055764'><status><basic>open</basic></status></tuple><dm:person id='p5e347748'><dm:note>Available</dm:note></dm:person></presence> Here is the code from parser/parse_event.c if ((_e->text.len == PRES_STR_LEN) && !strncasecmp(PRES_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_PRESENCE; } else if ((_e->text.len == PRES_XCAP_CHANGE_STR_LEN) && !strncasecmp(PRES_XCAP_CHANGE_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_XCAP_CHANGE; } else if ((_e->text.len == PRES_WINFO_STR_LEN) && !strncasecmp(PRES_WINFO_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_PRESENCE_WINFO; } else if ((_e->text.len == PRES_SIP_PROFILE_STR_LEN) && !strncasecmp(PRES_SIP_PROFILE_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_SIP_PROFILE; } else if ((_e->text.len == DIALOG_STR_LEN) && !strncasecmp(DIALOG_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_DIALOG; } else if ((_e->text.len == MWI_STR_LEN) && !strncasecmp(MWI_STR, tmp.s, _e->text.len)) { _e->parsed = EVENT_MWI; } else { _e->parsed = EVENT_OTHER; } if( (*end)== ';') { str params_str; params_str.s= end+1; end= skip_token(params_str.s, tmp.len- _e->text.len- 1); params_str.len= end- params_str.s; if (parse_params(&params_str, CLASS_ANY, &phooks, &_e->params)<0) return -1; } else _e->params= NULL; It detects presence event correctly, but then if( (*end)== ';') does not find any semicolon and here is the result: 10/13 16:34:57 13030 err ERROR:presence:handle_publish: <publish.c: 508> Missing or unsupported event header field value 10/13 16:34:57 13030 err ERROR:presence:handle_publish: <publish.c: 511> event=[presence] What semicolon it is looking? If I do (*end)== ' ') it still can't parse. Is Bria message has incorrect format? What was the format of message the parser was written for? Thanks a lot, Toly -- View this message in context: http://www.nabble.com/presence-module%2C-events-tp19963494p19963494.html Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.

16 years, 1 month

← Newer
1
...
9
10
11
12
13
14
15
16
17
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 October 2008