sr-users September 2007

sr-users@lists.kamailio.org

158 participants
247 discussions

[OpenSER-Users] example web_im send_im.html/php within openser 1.2.1 doensn't work

by CHEN XUEQIN

Hi all: I put example script file send_im.html/send_im.php in example/web_im direcotry into apache webroot. Then I launch firefox, fill in SIP Address and Message, click to send. But firefox don't response. The status bar indicated wait something. The fact is: 1. openser load mi_fifo.so correctly 2. the fifo file /tmp/openser_fifo, with the permission 0666, everyone can read and write 3. LOG message " DEBUG:mi_fifo:mi_fifo_server: entered consume", missing log "**** done consume" 4. SIP Address was user registered on openser. From Header was another user who registered on openser. 5. when I restart openser, replace fifo cmd with ":get_statistics:", send_im.php works Anyone know why? How to send message via fifo, pelease let me know Thanks in advance. Regards, Chen Xueqin

17 years, 2 months

Re: [OpenSER-Users] OpenSER with MySQL Cluster

by Helge Waastad

Hi My experiences with MySQL clusters is that you have to expand the index memory etc as far as you dear to enable adding new tables/columns etc. I guess yopu would not like to do that in a production evnvironment anyway... br hw

17 years, 2 months

[OpenSER-Users] user meeting (beer drinking in Vienna)

by Klaus Darilion

Hi! I proudly announce the first ser/openser/asterisk beer drinking evening in Vienna. When: Thursday (thirsty day) 20. September 2007, 19:00 CEST Where: Vienna, a bar in an inner district - exact location to be announced If you want to join please send a short reply so that I know for how many people I have to arrange a table. cu Klaus

17 years, 2 months

[Serusers] help needed in configuring ENUM with ENUM module

by geethanjali.csg＠wipro.com

Hi, I am trying to configure ser to use enum module. But I am getting the following error. 0(6192) get_record: lookup(5.6.7.8.e164.arpa, 35) failed 0(6192) enum_query(): No NAPTR record found for 5.6.7.8.e164.arpa. Can someone kindly give me some pointers to fix this error. I am trying this from past few days. Thanks, Geethanjali C S Wipro Technologies The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

17 years, 2 months

[OpenSER-Users] mediaproxy work for muti domains

by liu york

Dear all on my mind，mediaproxy can work for muti sip domains， like it's feature list―― -Ability to have different proxies for different SIP domains - Ability to use multiple proxy servers per SIP domain Now，using multiple proxy servers per SIP domain is ok for me，but i cant make it work with different SIP domains.Can somebody tell me how to do? mediaproxy.ini like below start = yes socket = /var/run/proxydispatcher.sock group = openser defaultProxy = domain://sip1.gteling.com the zone file in my dns like below mp1 IN A 64.77.236.132 mp2 IN A 210.51.163.165 sip1 IN A 64.77.236.132 sip2 IN A 210.51.163.165 _mediaproxy._tcp IN SRV 0 100 25060 mp1 how can i use use different medip proxy server for different sip domains. for example i want to use media mp1.gteling.com servise for sip domain sip1.gteling.com. many appreciation. 2007-09-19 york

17 years, 2 months

Re: [OpenSER-Users] WeSIP with openser 1.2.0 again

by Iñaki Baz Castillo

El Martes, 18 de Septiembre de 2007, Gregorio escribió: > Hi Elias et all, Please Gregorio, por future new questions to the list use the "New message" button in your Microsoft Office Outlook instead of replying to any other mail in the list and deleting body and subject. The mail you have sent has been created by pressing "Reply" over a mail with subject "Per branch timer and CANCEL on non final reply", so your mail appears in the same thread because it has a header: In-Reply-To: <293670490709180215t1536dff5ycd01a8bded247cfa(a)mail.gmail.com> For people using thread capable mail clients this is very uncomfortable. Even, you can see how wrong it is by looking for your mail in the mail archive: http://openser.org/pipermail/users/2007-September/thread.html (note how your mail "WeSIP with openser 1.2.0 again" hangs from "Per branch timer and CANCEL on non final reply", being it really wrong). So please, for future **new** questions use "New message" and just use "Reply" when you really want to reply a previous mail. PD: Using HTML and blue text is not very appreciated by people reading lost of mail each day. Please, use plain text. Regards. -- Iñaki Baz Castillo

17 years, 2 months

[OpenSER-Users] OSPToolkit Warning Messages

by Edson

Hi... I'm trying to compile OSP support for eather 1.2.2 or TRUNK. I have OpenSSL 0.9.8d on a OpenSUSE 10.2. I was wondering if the warning that pops are something that desire attention, since are related to the X509 part: ospopenssl.c: In function âbio_dump_cbâ: ospopenssl.c:597: warning: format â%08Xâ expects type âunsigned intâ, but argument 3 has type âstruct BIO *â ospopenssl.c:597: warning: format â%08lXâ expects type âlong unsigned intâ, but argument 4 has type âconst char *â ospopenssl.c:597: warning: format â%Xâ expects type âunsigned intâ, but argument 7 has type âlong intâ ospopenssl.c:604: warning: format â%08Xâ expects type âunsigned intâ, but argument 3 has type âstruct BIO *â ospopenssl.c:604: warning: format â%08lXâ expects type âlong unsigned intâ, but argument 4 has type âconst char *â ospopenssl.c:604: warning: format â%Xâ expects type âunsigned intâ, but argument 7 has type âlong intâ ospopenssl.c: In function âOSPPSSLLoadCertsâ: ospopenssl.c:659: warning: passing argument 2 of âd2i_X509â from incompatible pointer type ospopenssl.c:689: warning: passing argument 2 of âd2i_X509â from incompatible pointer type Any glues or nothing to worry about??? Edson

17 years, 2 months

[OpenSER-Users] snmpstats agent failing to connect to master agent

by Gabi Mahu

Hello all, I am currently trying to get the snmpstats module up and running, for monitoring purposes. I followed the instructions in the module documentation, I studied Net-SNMP references and I searched web resources for several days now, but still I couldn't succeed in starting the openser module properly. I have no idea what the problem could be. The NET-SNMP part of the equation seams to work properly: I am using the 5.4.1 version. I managed to play around with the tools from the package, in local and remote scenarios too. I was able to send and receive traps, get and set different values in the MIB tree, load new MIBs... On the openser part, I'm not doing something special. I have a config file that does nothing, except load the snmpstats module and set the limits for the dialogs and the unparsed data traps. That's it. I tried with fork on yes and on no, because I found out from my web searches that this could be a problem, but all I got was some logging in the no fork scenario, saying that the snmp agent from snmpstats could not connect to the master agent, the snmpd that runs on the same machine. The "check for a proper configuration" step in the module documentation failed also, before this (I got no output in the snmpd window after openser was started, until that point, everything was like in the documentation), so this couldn't work actually, but i still did it anyway. The problem must be in the configuration files, but it escapes me. This is the content of the files (yes, both in the same location...): snmpd.conf ----------------------------------- com2sec notConfigUser default public group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser view systemview included .1.3.6.1.2.1.1 view systemview included .1.3.6.1.2.1.25.1.1 access notConfigGroup "" any noauth exact systemview none none syslocation localhost (edit /etc/snmp/snmpd.conf) syscontact Root <root@localhost> (configure /etc/snmp/snmp.local.conf) pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat rocommunity public localhost trapsink localhost:162 public trap2sink localhost:162 public authtrapenable 1 master agentx ---------------------------------------------- snmpstats.conf ------------------------------- agentXSocket tcp:localhost:705 ---------------------------------------------- And the way I start snmpd now is: snmpd -f -Lo -M /usr/local/share/mibs -m ALL -d -x tcp:localhost:705 I did try several versions including the one found in the module documentation. This is the context of my problem. Hopping that there is a small, but obvious mistake, in my config files, due to my lack of attention or something, and not a more serious thing, I thank you for your time. Gabriel Mahu --------------------------------- Check out the hottest 2008 models today at Yahoo! Autos.

17 years, 2 months

Re: [OpenSER-Users] WeSIP with openser 1.2.0 again

by Elias Baixas

Hi Gregorio, can you send over the logs but with the 'debug' variable set to 7 ? I couldn't see the SIP messages in the logs you sent me. Elias Gregorio wrote: > > Hi Elias et all, > > > > I still get the parsing exception in the SEAS module when SIP MESSAGE > are sent from Openser to WeSIP. If I could know which header fail, > perhaps I could find a temporal solution and go on withw the > development, Elias can you tell me something about this? > > > > Thanks a lot for the help. > > Regards. > > Gregorio. > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

17 years, 2 months

[OpenSER-Users] OpenXCAP problem

by mika.saari＠wipsl.com

Hi, I have "successfully" installed OpenXCAP with latest OpenSER SVN. The OpenXCAP server manages to contact the SQL server. When I am using EyeBeam 1.5 with setting "http://openxcap.mydomain.com:8000/xcap-root/" I get next error to the syslog. Sep 18 14:17:21 openxcap openxcap[9902]: [-] error: Invalid Document Selector /xcap-root/resource-lists/users/testacc/buddies-resource-list.xml (the Document Selector context must be 'users' or 'global') What kind of misconfiguration I have done ? Thanks a lot, -Mika

17 years, 2 months

← Newer
1
...
10
11
12
13
14
15
16
...
25
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 September 2007