sr-users January 2004

sr-users@lists.kamailio.org

142 participants
338 discussions

[Serusers] dbtext module
by Annie Sasidar 27 Jan '04

27 Jan '04

Hi, I want to use the dbtext module.Since i use this module i cannot use serweb and have to use the db-api. Just like serctl commands for mysql is there any commands i can use with dbtext module so as to add users. Basically how do i use the db-api? Experts please shed some light. Thanks in advance, Annie

2 1

[Serusers] [MailServer Notification] To Recipient a virus was found and acti on taken.
by System Attendant 27 Jan '04

27 Jan '04

ScanMail for Microsoft Exchange took action on the message. The message details were: Sender = serusers(a)lists.iptel.org Recipient(s) = serusers(a)lists.iptel.org; Subject = [Serusers] Returned mail: see transcript for details Scanning time = 01/27/2004 05:06:47 Engine/Pattern = 6.810-1005/745 Action taken on message: The attachment body.pif contained WORM_MIMAIL.R virus. ScanMail took the action: Deleted. Warning to recipient. ScanMail has detected a virus.

1 0

RE: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more
by Klaus Darilion 27 Jan '04

27 Jan '04

Put into the ser proxy a second NIC and configure it as IPv6 only. enable Record-route and ser will do the v4-v6 translation. For establishing an RTP-stream between v4 and v6 clients you can use rtpproxy. Take a look of the recent rtpproxy thread in the mailing list, there are some explanations what is already supported by rtpproxy and what has to be done. klaus > -----Original Message----- > From: CURRO_DOMINGUEZ [mailto:CURRO_DOMINGUEZ@terra.es] > Sent: Tuesday, January 27, 2004 10:49 AM > To: Jan Janak; serusers(a)lists.iptel.org > Subject: Re: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more > > > Ouch!! Not IPv4/IPv6 translation of SDP addresses? > > Thanks Klaus and Jan for your answers. Well, I thought on a > device with > 2 network cards because I want to divide IPv6 and IPv4 networks. > > Do you know whether SER is going to be able to translate SDP > addresses > in the near future? > > I have another question. Is the SIP IPv4 server a mandatory device in > this scenario? I mean, I think I can use the SIP IPv6 server and the > IPv6/IPv4 translator and nothing else. In this way, IPv4 > devices would > have the translator as SIP Proxy, and the translator would redirect > thier request to the IPv6 SIP server. So there would be one > domain and > one registrar. > > What do you think about this? Is this possible? > > Thank you very much > > Curro > > ----- Mensaje Original ----- > De: Jan Janak <jan(a)iptel.org> > Fecha: Lunes, Enero 26, 2004 12:53 pm > Asunto: Re: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more > > > As mentioned by Klaus, one network device with both IPv4 and IPv6 > > addresses will do the job. You then need to configure ser to > > listen on > > both of them and make sure that record-routing is enabled. > > > > SER can translate SIP signalling, what it can not done yet is IPv4- > > IPv6translation of SDP addresses. > > > > Jan. > > > > On 26-01 11:00, Klaus Darilion wrote: > > > You don't need two network cards, one is enough. This interface > > must be > > > configured with an IPv4 and an IPv6 address. > > > > > > Klaus > > > > > > > -----Original Message----- > > > > From: CURRO_DOMINGUEZ [mailto:CURRO_DOMINGUEZ@terra.es] > > > > Sent: Monday, January 26, 2004 10:49 AM > > > > To: serusers(a)lists.iptel.org > > > > Subject: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more > > > > > > > > > > > > Hello > > > > > > > > After installing and running over last month SER, we are going > > to the > > > > next step. Our final goal is to deploy a SIP network which > > allows SIP > > > > clients Voice Call, Videoconference (RTP), Instant Message and > > > > Presence. And we want to use IPv6 and IPv4 networks. > > > > > > > > I wonder several questions about this: > > > > > > > > I'll use a SER server for IPv4 network and another for IPv6 > > network, > > > > but how I connect them? I think that I need a device with two > > network > > > > cards connected each one to IPv4 or IPv6. Which software has > > to run > > > > this device to act as a SIP Protocol Gateway? Can SER do this? > > > > > > > > Do you think that with the two proxy SER servers and the SIP > > Protocol > > > > Gateway would be enough or that I need another device to > > > > develope this? > > > > > > > > Thank you very much for your time and responses > > > > > > > > Curro > > > > > > > > > > > > _______________________________________________ > > > > Serusers mailing list > > > > serusers(a)lists.iptel.org > > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > >

1 0

Re: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more
by CURRO_DOMINGUEZ 27 Jan '04

27 Jan '04

Ouch!! Not IPv4/IPv6 translation of SDP addresses? Thanks Klaus and Jan for your answers. Well, I thought on a device with 2 network cards because I want to divide IPv6 and IPv4 networks. Do you know whether SER is going to be able to translate SDP addresses in the near future? I have another question. Is the SIP IPv4 server a mandatory device in this scenario? I mean, I think I can use the SIP IPv6 server and the IPv6/IPv4 translator and nothing else. In this way, IPv4 devices would have the translator as SIP Proxy, and the translator would redirect thier request to the IPv6 SIP server. So there would be one domain and one registrar. What do you think about this? Is this possible? Thank you very much Curro ----- Mensaje Original ----- De: Jan Janak <jan(a)iptel.org> Fecha: Lunes, Enero 26, 2004 12:53 pm Asunto: Re: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more > As mentioned by Klaus, one network device with both IPv4 and IPv6 > addresses will do the job. You then need to configure ser to > listen on > both of them and make sure that record-routing is enabled. > > SER can translate SIP signalling, what it can not done yet is IPv4- > IPv6translation of SDP addresses. > > Jan. > > On 26-01 11:00, Klaus Darilion wrote: > > You don't need two network cards, one is enough. This interface > must be > > configured with an IPv4 and an IPv6 address. > > > > Klaus > > > > > -----Original Message----- > > > From: CURRO_DOMINGUEZ [mailto:CURRO_DOMINGUEZ@terra.es] > > > Sent: Monday, January 26, 2004 10:49 AM > > > To: serusers(a)lists.iptel.org > > > Subject: [Serusers] SER, IPv6, IPv6/IPv4 interworking and more > > > > > > > > > Hello > > > > > > After installing and running over last month SER, we are going > to the > > > next step. Our final goal is to deploy a SIP network which > allows SIP > > > clients Voice Call, Videoconference (RTP), Instant Message and > > > Presence. And we want to use IPv6 and IPv4 networks. > > > > > > I wonder several questions about this: > > > > > > I'll use a SER server for IPv4 network and another for IPv6 > network, > > > but how I connect them? I think that I need a device with two > network > > > cards connected each one to IPv4 or IPv6. Which software has > to run > > > this device to act as a SIP Protocol Gateway? Can SER do this? > > > > > > Do you think that with the two proxy SER servers and the SIP > Protocol > > > Gateway would be enough or that I need another device to > > > develope this? > > > > > > Thank you very much for your time and responses > > > > > > Curro > > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers >

2 1

RE: [Serusers] Sems
by Joao Sampaio 27 Jan '04

27 Jan '04

I'm sill working on this so I don't know if my conf files will work. But I'm following the example on http://iptel.org/~faqomatic/fom-serve/cache/92.html . Take a look. João -----Original Message----- From: 'Atle Samuelsen' [mailto:clona@cyberhouse.no] Sent: segunda-feira, 26 de Janeiro de 2004 17:47 To: Joao Sampaio Subject: Re: [Serusers] Sems btw, off the list: How does your config look with the voicemail in ser? does it automaticly redirect to voicemail after XX seconds? if so. could you send me the needed in that config to get to work ? - Atle * 'Atle Samuelsen' <clona(a)cyberhouse.no> [040126 18:39]: > Hm > did'nt have that problem.. Tho.. have you checked your database that > your user 1001 has a e-mail address? > > > > - Atle > > * Joao Sampaio <est-j-sampaio(a)ptinovacao.pt> [040126 18:29]: > > Hello, thanks. > > > > I found my problem (till now!) which was a bad sems configuration file. > > > > Now voicemail is responding to the calls but I always get the message > > "Session rejected: 404 voicemail: no email address for user <1001> " on the > > caller phone. > > > > Did you have the same problem? > > > > Thanks > > > > Jo?o > > > > > > > > -----Original Message----- > > From: Atle Samuelsen [mailto:clona@cyberhouse.no] > > Sent: segunda-feira, 26 de Janeiro de 2004 17:22 > > To: Joao Sampaio > > Subject: Re: [Serusers] Sems > > > > > > > > it looks like the same problem I had yesterday.. > > > > If I did understand the README file, I think the sems CVS and SER CVS > > works together but not SER no-Cvs + SEMS CVS. this is because of the > > upgrade of the fifo buffer thing. > > > > > > - ATle > > > > > > .. here's my modified default config.. > > > > > > > > # $Id: sems.conf.sample,v 1.11 2003/11/19 19:03:22 rco Exp $ > > # > > # sems.conf.sample > > # > > # Sip Express Media Server (sems) > > # > > # sample configuration file > > # > > # > > # whitespaces (spaces and tabs) are ignored > > # comments start with a "#" and may be used inline > > # > > # example: option=value1, value2 # i like this option > > # > > > > ################################## > > # global parameters # > > ################################## > > > > # optional parameter: fork={yes|no} > > # > > # - specifies if sems should run in daemon mode (background) > > # (fork=no is the same as -E) > > fork=yes > > > > # optional parameter: stderr={yes|no} > > # > > # - debug mode: do not fork and log to stderr > > # (stderr=yes is the same as -E) > > stderr=no > > > > # optional parameter: loglevel={0|1|2|3} > > # > > # - sets log level (error=0, warning=1, info=2, debug=3) > > # (same as -D) > > loglevel=1 > > > > # optional parameter: fifo_name=<filename> > > # > > # - path and file name of our fifo file (same as -i) > > fifo_name=/tmp/am_fifo > > > > # optional parameter: ser_fifo_name=<filename> > > # > > # - path and file name of Ser's fifo file (same as -o) > > ser_fifo_name=/tmp/ser_fifo > > > > # optional parameter: plugin_path=<path> > > # > > # - sets the path to the plug-ins > > # - may be absolute or relative to CWD > > plugin_path=/usr/local/lib/sems/plug-in > > > > # optional parameter: smtp_server=<hostname> > > # > > # - sets address of smtp server > > smtp_server=localhost > > > > # optional parameter: smtp_port=<port> > > # > > # - sets port of smtp server > > smtp_port=25 > > > > > > ################################## > > # module specific parameters # > > ################################## > > > > # sample voicemail configuration (inline) > > config.voicemail=inline > > > > # optional parameter: announce_path=<path> > > # > > # - sets the path where announce files are searched for > > # - the file to be played is determined the following way: > > # <announce_path>/<domainname>/<username>.wav > > # if this file is not available <announce_path>/<default_anounce> is > > # used > > announce_path=/usr/local/lib/sems/audio/ > > > > # parameter: default_announce=<filename> > > # > > # - sets the name of the default announce WAV file > > default_announce=default.wav > > > > # parameter: max_record_time=<seconds> > > # > > # - maximum record time > > max_record_time=30 > > > > # end of configuration section for voicemail module > > config.voicemail=end > > > > > > # sample announcement configuration (inline) > > config.announcement=inline > > > > # optional parameter: announce_path=<path> > > # > > # - sets the path where announce files are searched for > > announce_path=/usr/local/lib/sems/audio/ > > > > # parameter: default_announce=<filename> > > # > > # - sets the name of the default announce WAV file > > default_announce=default.wav > > > > # end of configuration section for announcement module > > config.announcement=end > > > > > > # sample isdngw module configuration (external file) > > # config.isdngw=/etc/isdngw.conf > > > > # sample ivr module configuration (inline) > > config.ivr=inline > > > > #parameter: python_script_path=<full path> > > python_script_path=/etc/ivr > > > > #parameter: python_script_file=<filename> > > python_script_file=example.py > > > > # end of configuration section for ivr module > > config.ivr=end > > > > > > # sample conference configuration (inline) > > config.conference=inline > > > > # parameter: default_announce=<filename> > > # > > # - sets the full pathed name of the default announce WAV file. > > # Will be played to lonely users. > > default_announce=/usr/local/lib/sems/audio/first_participant.wav > > > > > > # end of configuration section for conference module > > config.conference=end > > > > # example configuration for number reader > > config.number_reader=inline > > > > number_path=/usr/local/lib/sems/audio/ > > > > prolog_file=/usr/local/lib/sems/audio/welcome_to_number_reader.wav > > > > epilog_file=/usr/local/lib/sems/audio/thanks_calling_number_reader.wav > > > > # end of number_reader configuration > > config.number_reader=end > > > > # add more module configurations here (inline or external): > > # > > # config.mymodule=<filename> > > # or > > # config.mymodule=inline > > # ... > > # config.mymodule=end > > > > > > > > > > * Joao Sampaio <est-j-sampaio(a)ptinovacao.pt> [040126 15:43]: > > > > > > Hello, > > > > > > I'm trying to install sems so that I can configure my ser proxy to support > > > voicemail functions. > > > > > > I have downloaded the last CVS version of sems and I'm currently running > > ser > > > version 0.8.12 > > > > > > I got these error every time I try to start sems: > > > > > > Sems[12051]: Warning: /etc/sems/sems.conf:59 configuration: ignoring > > > unknown parameter announce_path > > > Sems[12051]: Warning: /etc/sems/sems.conf:64 configuration: ignoring > > > unknown parameter default_announce > > > Sems[12051]: Warning: /etc/sems/sems.conf:69 configuration: ignoring > > > unknown parameter max_record > > > Sems[12054]: Warning: no configuration found for module announcement, > > maybe > > > you want to specify config.announcement in config file. > > > Sems[12054]: Error: while loading plug-in > > > '/usr/local/lib/sems/plug-in/apps/announcement.so' > > > Sems[12053]: Warning: signal 17 received > > > > > > > > > Another question: Is ser 0.8.12 compatible with the last version of sems > > in > > > CVS? > > > > > > Thank you very much. > > > > > > Best reagards, > > > _______________________ > > > Jo?o Sampaio > > > > > > PT Inova??o, SA > > > > > > SRM - Servi?os e Redes M?veis > > > > > > email: est-j-sampaio(a)ptinovacao.pt > > > Tlf: +351 234511160-1907 / +351 234403421 > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers >

3 4

[Serusers] radius_authorize_sterman(): Failure
by Gregory D. Burns 27 Jan '04

27 Jan '04

Guys, Im trying to setup radius Authenticate but cant figure out why I keep getting the below error. I have SER 0.12 and freeradius 0.9.3 installed on the same server. What could I be missing? Freeradius has this config in the user file: greg Auth-Type := Digest, User-Password == "xxxxx" Reply-Message = "Authenticated" Debug: 0(6147) SIP Request: 0(6147) method: <REGISTER> 0(6147) uri: <sip:64.81.88.148> 0(6147) version: <SIP/2.0> 0(6147) parse_headers: flags=1 0(6147) end of header reached, state=5 0(6147) parse_headers: Via found, flags=1 0(6147) parse_headers: this is the first via 0(6147) After parse_msg... 0(6147) preparing to run routing scripts... 0(6147) logging so message came in 0(6147) DEBUG : is_maxfwd_present: searching for max_forwards header 0(6147) parse_headers: flags=128 0(6147) end of header reached, state=9 0(6147) DEBUG: get_hdr_field: <To> [36]; uri=[sip:2012@64.81.88.148;user=phone] 0(6147) DEBUG: to body [<sip:2012@64.81.88.148;user=phone> ] 0(6147) get_hdr_field: cseq <CSeq>: <12> <REGISTER> 0(6147) DEBUG: get_hdr_body : content_length=0 0(6147) found end of header 0(6147) DEBUG: is_maxfwd_present: max_forwards header not found! 0(6147) DEBUG: add_param: tag=2161114233 0(6147) end of header reached, state=29 0(6147) parse_headers: flags=256 0(6147) find_first_route(): No Route headers found 0(6147) loose_route(): There is no Route HF 0(6147) check_nonce(): comparing [4015e5a000c7aec015d8da7e158f8720532f4d22] and [4015e5a000c7aec015d8da7e158f8720532f4d22] 0(6147) res: -2 0(6147) radius_authorize_sterman(): Failure 0(6147) build_auth_hf(): 'WWW-Authenticate: Digest realm="64.81.88.148", nonce="4015e5a1ed5da080d2f74b1e0a65e54e4b4bae8f", qop="auth" ' It looks like the radius server is working ok : rlm_digest: Converting Digest-Attributes to something sane... Digest-User-Name = "greg" Digest-Realm = "64.81.88.148" Digest-Nonce = "4015e5a000c7aec015d8da7e158f8720532f4d22" Digest-Uri = "sip:64.81.88.148" Digest-Method = "REGISTER" Digest-Qop = "auth" Digest-Nonce-Count = "00000001" Digest-Cnonce = "05efa56c" modcall[authorize]: module "digest" returns ok for request 108 rlm_realm: Proxy reply, or no User-Name. Ignoring. modcall[authorize]: module "suffix" returns noop for request 108 users: Matched DEFAULT at 152 users: Matched greg at 214 modcall[authorize]: module "files" returns ok for request 108 modcall[authorize]: module "mschap" returns noop for request 108 modcall: group authorize returns ok for request 108 rad_check_password: Found Auth-Type Digest rad_check_password: Auth-Type = Accept, accepting the user radius_xlat: 'Authenticated' Sending Access-Accept of id 25 to 127.0.0.1:4720 Reply-Message = "Authenticated" Finished request 108

2 1

[Serusers] File blocked - ScanMail for Lotus Notes --> hi
by Mail System 27 Jan '04

27 Jan '04

The file that was attached to the mail item below has been removed by Singapore Press Holdings Ltd mail gateway either because it is not permitted by our security policy or may contain a virus. This is a system generated mail, please do not reply. Date: 27/01/2004 08:58:52 AM 121: hi Virus: Blocked; File: body.scr From: serusers(a)lists.iptel.org To: sandra(a)sph.com.sg 123: Sandra_Davie_P(a)smtp2.sph.com.sg Action: Blocked; Scanned by ScanMail for Lotus Notes 2.51 with scanengine 6.510-1002 and patternfile lpt$vpn.741 NOTE: Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. All opinions, conclusions and other information expressed in this message not of an official nature shall not be deemed as given or endorsed by SPH unless otherwise indicated by an authorised representative independent of this message.

1 0

[Serusers] WARNING. You tried to send a potential virus or unauthorised code
by alert＠notification.messagelabs.com 26 Jan '04

26 Jan '04

The MessageLabs SkyScan Anti-Virus service discovered a possible virus or unauthorised code (such as a joke program or trojan) in an email sent by you. The email has now been quarantined and was not delivered. Please read the whole of this email carefully. It explains what has happened to your email, which suspected virus has been caught and what to do if you need help addressing the problem. To help identify the quarantined email: The message sender was serusers(a)lists.iptel.org The message recipients were lizzie.vann(a)organixbrands.com The message title was Test The message date was Mon, 26 Jan 2004 18:56:38 -0500 The virus or unauthorised code identified in the email is /var/qmail/queue/split/0/attach/325227_3X_AZ-S_PA2__body.scr Found the W32/Mydoom@MM virus !!! Some viruses forge the sender address. For more information please visit the link to the virus FAQ's at the bottom of this page. The message was diverted into the virus holding pen on mail server server-2.tower-21.messagelabs.com (pen id 325227_1075161381) and will be held for 30 days before being destroyed Corporate Users: If you sent the email from a corporate network, you should first contact your local IT Helpdesk or System Administrator for advice. They will be able to help you disinfect your workstation. If you would like further information on how to subscribe to MessageLabs SkyScan AV service, a proactive anti-virus service working around the clock, around the globe, please visit http://www.messagelabs.com/page.asp?id=323 Personal or Home users: If you sent the email from a personal or home account, you will need to disinfect your computer yourself. Please contact your anti-virus software vendor for support. You may like to read the virus FAQ's at: http://www.messagelabs.com/page.asp?id=628 which will answer most virus related questions. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________

1 0

[Serusers] WARNING. You tried to send a potential virus or unauthorised code
by alert＠notification.star.net.uk 26 Jan '04

26 Jan '04

The Star Internet anti-virus service, powered by MessageLabs, discovered a possible virus or unauthorised code (such as a joke program or trojan) in an email sent by you. This email has now been quarantined and was not delivered. Please read this whole email carefully. It explains what has happened to your email, which suspected virus has been caught, and what to do if you need help. To help identify the email: The message sender was serusers(a)lists.iptel.org The message was titled 'TEST' The message date was Mon, 26 Jan 2004 16:26:59 -0700 The message recipients were mcoffey(a)interactiveser.com The virus or unauthorised code identified in the email is: F-Secure Anti-Virus for Linux version 4.51 build 2312 Copyright (c) 1999-2003 F-Secure Corporation. All Rights Reserved. Database version: 2004-01-27_01 Scan started at Mon Jan 26 23:27:08 2004 attach/487773_2X_PM4_EMS_MA-OCTET=2DSTREAM__tpazyb.scr: Infected: W32/Mydoom.A@mm [Orion] Scan ended at Mon Jan 26 23:27:09 2004 1 file scanned 1 file infected Some viruses forge the sender address. The message was diverted into the virus holding pen on mail server server-6.tower-19.messagelabs.com (id 487773_1075159628) and will be held for 30 days before being destroyed. For more information please visit http://www.star.net.uk/Support/Faq/FAQ.asp If you sent the email from a corporate network, please contact your IT Helpdesk or Support Department for assistance. They will be able to help you disinfect your workstation. If you would like further information on how to subscribe to the Star Internet anti-virus service, a proactive anti-virus service working around the clock, around the globe, please complete our enquiry form Star Internet is a business to business service provider. If you are a home user you should contact your anti-virus software vendor or obtain help from http://www.star.net.uk/Support/Faq/FAQ.asp ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________

1 0

RE: [Serusers] Sems
by Joao Sampaio 26 Jan '04

26 Jan '04

Hello, thanks. I found my problem (till now!) which was a bad sems configuration file. Now voicemail is responding to the calls but I always get the message "Session rejected: 404 voicemail: no email address for user <1001> " on the caller phone. Did you have the same problem? Thanks João -----Original Message----- From: Atle Samuelsen [mailto:clona@cyberhouse.no] Sent: segunda-feira, 26 de Janeiro de 2004 17:22 To: Joao Sampaio Subject: Re: [Serusers] Sems it looks like the same problem I had yesterday.. If I did understand the README file, I think the sems CVS and SER CVS works together but not SER no-Cvs + SEMS CVS. this is because of the upgrade of the fifo buffer thing. - ATle .. here's my modified default config.. # $Id: sems.conf.sample,v 1.11 2003/11/19 19:03:22 rco Exp $ # # sems.conf.sample # # Sip Express Media Server (sems) # # sample configuration file # # # whitespaces (spaces and tabs) are ignored # comments start with a "#" and may be used inline # # example: option=value1, value2 # i like this option # ################################## # global parameters # ################################## # optional parameter: fork={yes|no} # # - specifies if sems should run in daemon mode (background) # (fork=no is the same as -E) fork=yes # optional parameter: stderr={yes|no} # # - debug mode: do not fork and log to stderr # (stderr=yes is the same as -E) stderr=no # optional parameter: loglevel={0|1|2|3} # # - sets log level (error=0, warning=1, info=2, debug=3) # (same as -D) loglevel=1 # optional parameter: fifo_name=<filename> # # - path and file name of our fifo file (same as -i) fifo_name=/tmp/am_fifo # optional parameter: ser_fifo_name=<filename> # # - path and file name of Ser's fifo file (same as -o) ser_fifo_name=/tmp/ser_fifo # optional parameter: plugin_path=<path> # # - sets the path to the plug-ins # - may be absolute or relative to CWD plugin_path=/usr/local/lib/sems/plug-in # optional parameter: smtp_server=<hostname> # # - sets address of smtp server smtp_server=localhost # optional parameter: smtp_port=<port> # # - sets port of smtp server smtp_port=25 ################################## # module specific parameters # ################################## # sample voicemail configuration (inline) config.voicemail=inline # optional parameter: announce_path=<path> # # - sets the path where announce files are searched for # - the file to be played is determined the following way: # <announce_path>/<domainname>/<username>.wav # if this file is not available <announce_path>/<default_anounce> is # used announce_path=/usr/local/lib/sems/audio/ # parameter: default_announce=<filename> # # - sets the name of the default announce WAV file default_announce=default.wav # parameter: max_record_time=<seconds> # # - maximum record time max_record_time=30 # end of configuration section for voicemail module config.voicemail=end # sample announcement configuration (inline) config.announcement=inline # optional parameter: announce_path=<path> # # - sets the path where announce files are searched for announce_path=/usr/local/lib/sems/audio/ # parameter: default_announce=<filename> # # - sets the name of the default announce WAV file default_announce=default.wav # end of configuration section for announcement module config.announcement=end # sample isdngw module configuration (external file) # config.isdngw=/etc/isdngw.conf # sample ivr module configuration (inline) config.ivr=inline #parameter: python_script_path=<full path> python_script_path=/etc/ivr #parameter: python_script_file=<filename> python_script_file=example.py # end of configuration section for ivr module config.ivr=end # sample conference configuration (inline) config.conference=inline # parameter: default_announce=<filename> # # - sets the full pathed name of the default announce WAV file. # Will be played to lonely users. default_announce=/usr/local/lib/sems/audio/first_participant.wav # end of configuration section for conference module config.conference=end # example configuration for number reader config.number_reader=inline number_path=/usr/local/lib/sems/audio/ prolog_file=/usr/local/lib/sems/audio/welcome_to_number_reader.wav epilog_file=/usr/local/lib/sems/audio/thanks_calling_number_reader.wav # end of number_reader configuration config.number_reader=end # add more module configurations here (inline or external): # # config.mymodule=<filename> # or # config.mymodule=inline # ... # config.mymodule=end * Joao Sampaio <est-j-sampaio(a)ptinovacao.pt> [040126 15:43]: > > Hello, > > I'm trying to install sems so that I can configure my ser proxy to support > voicemail functions. > > I have downloaded the last CVS version of sems and I'm currently running ser > version 0.8.12 > > I got these error every time I try to start sems: > > Sems[12051]: Warning: /etc/sems/sems.conf:59 configuration: ignoring > unknown parameter announce_path > Sems[12051]: Warning: /etc/sems/sems.conf:64 configuration: ignoring > unknown parameter default_announce > Sems[12051]: Warning: /etc/sems/sems.conf:69 configuration: ignoring > unknown parameter max_record > Sems[12054]: Warning: no configuration found for module announcement, maybe > you want to specify config.announcement in config file. > Sems[12054]: Error: while loading plug-in > '/usr/local/lib/sems/plug-in/apps/announcement.so' > Sems[12053]: Warning: signal 17 received > > > Another question: Is ser 0.8.12 compatible with the last version of sems in > CVS? > > Thank you very much. > > Best reagards, > _______________________ > Jo?o Sampaio > > PT Inova??o, SA > > SRM - Servi?os e Redes M?veis > > email: est-j-sampaio(a)ptinovacao.pt > Tlf: +351 234511160-1907 / +351 234403421 > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

2 1

← Newer
1
...
6
7
8
9
10
11
12
...
34
Older →

Jump to page:

2025

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 January 2004