July 2005 - sr-users - kamailio.org

[Serusers] Carrier-grade framework for SER
by Andreas Granig 27 Sep '06

27 Sep '06

Hi guys, I'd like to propose another possibility for a highly-available and scalable system design based on SER: The problems I've encountered for scalable systems are: - Distribution of the user location and alias location among the nodes (user location is based on registrations, alias location comes from web interfaces and is used for call forwarding). - Reloading up to date location tables after breakdown and recovery of a node So I'm just thinking loud about the following provisioning system: - Write a client which fulfills the this demands: - Receive one or more locations from SER via a SER module or from a web application and distribute them to other known clients. Take care of retransmissions if a client isn't reachable or reports a temporary failure. - Receive one or more locations from other clients and write them into the SER FIFO. If writing into the FIFO fails, try to write directly into the database (location-table, alias-table etc.). Report a temporary failure if this also fails. Maybe a centralized server should be used which receives the locations from the clients and distributes them to other clients, so that the nodes just know about the server and nothing about other nodes. This would make integration of new nodes easy. On the other hand, it's another single point of failure, so a decentralized solution should be considered. But that would mean that you've to inform every node about the existence of a new node. The protocol used between the nodes should be simple and fast. So I think SOAP drops out here. Maybe XMLRPC or ICE (http://www.zeroc.com/ice.html) could be used. One might think now why not just use replication on SIP layer, but t_replicate only supports one peer and you've no possibility to get locations on a node while it's down. Replication of other location tables like the alias-table is also not possible. I'd be willing to release these parts as GPL for creating an open framework for carrier-grade SER integration, so any feedback, improvements or flames are highly welcome. Cheers, Andy

13 37

[Serusers] Modifying "From" header field of an INVITE message
by scm-j＠nuntius.com 04 May '06

04 May '06

I am relatively new to SER. My SIP service provider requires me to present the ANI in the "From" field in my INVITE message header in E.164 format. I am currently sending this information as follows: From: "2125551212" <sip:2125551212@xxx.xxx.xxx.xxx> They want it in E.164 format as follows: From: "+12125551212" <sip:+12125551212@xxx.xxx.xxx.xxx> I see function only to modify the SIP URI but not the other header or SDP fields. Could someone help me with a code snippet that I can use in ser.cfg to do this conversion? Regards, SCM

7 8

RE: [Serusers] msilo, voicemail and serweb
by Alejandro Mellado 24 Jan '06

24 Jan '06

Yes, On serweb acount tab message store. I've seen the voicemail plugin code, and this doesn't write on mysql silo table. How I do put voicemail on serweb? Regards Alejandro. El sáb, 23-07-2005 a las 11:46 +0200, harry gaillac escribió: > Hello, > > You mean forward to voicemail on account tab ? > > harry > --- Alejandro Mellado <amellado(a)uct.cl> a écrit : > > > Hi > > > > > > I'm trying to activate the voicemail in serweb. > > I've working msilo with IM successfully. > > > > Somebody Can help me? > > > > > > Regards > > Saluda Atte. > > Alejandro Mellado <amellado(a)uct.cl>. > > Escuela de Informática > > Universidad Católica de Temuco > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > ___________________________________________________________________________ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.com Saluda Atte. Alejandro Mellado <amellado(a)uct.cl>. Escuela de Informática Universidad Católica de Temuco

2 2

[Serusers] Authenticate to Active Directory
by Bob McCormick 05 Dec '05

05 Dec '05

Does anyone know if there is a way to authenticate SER to MS Active Directory? I'd like to use an existing user database instead of having to manage users myself, and most of our users are in Active Directory. Has anyone tried this? What are most SER users using for authentication? Is anyone here tying into any kind of existing organization user database?

4 3

[Serusers] ser as outbound proxy only
by jeff kwong 26 Nov '05

26 Nov '05

Hi to everybody! Im currently trying to setup an outbound proxy using ser. Im still a newbie with this ser and im not yet that good with the scripting. Could anyone tell me how to configure ser for outbound proxy only using rtpproxy? There are samples files in the Getting started manual but im having troubles eliminating the authentication/mysql part in script since im not yet familiar which modules depends on which. A striped down version of the nat-rtpproxy.cfg file would be really appreciated. Thanks in advance. _jeff

6 8

[Serusers] Solaris8/SPARC compilation
by Ryan Pagquil 20 Sep '05

20 Sep '05

Hi guys, I'm having a problem with SER-0.9.3 installation in Solaris8/SPARC i've got these errors: bash-2.03# make all Makefile.rules:84: action.d: No such file or directory Makefile.rules:84: crc.d: No such file or directory Makefile.rules:84: daemonize.d: No such file or directory Makefile.rules:84: data_lump.d: No such file or directory Makefile.rules:84: data_lump_rpl.d: No such file or directory Makefile.rules:84: dprint.d: No such file or directory Makefile.rules:84: dset.d: No such file or directory Makefile.rules:84: error.d: No such file or directory Makefile.rules:84: fifo_server.d: No such file or directory Makefile.rules:84: flags.d: No such file or directory Makefile.rules:84: forward.d: No such file or directory Makefile.rules:84: hash_func.d: No such file or directory Makefile.rules:84: ip_addr.d: No such file or directory Makefile.rules:84: main.d: No such file or directory Makefile.rules:84: md5.d: No such file or directory Makefile.rules:84: md5utils.d: No such file or directory Makefile.rules:84: modparam.d: No such file or directory Makefile.rules:84: msg_translator.d: No such file or directory Makefile.rules:84: pass_fd.d: No such file or directory Makefile.rules:84: proxy.d: No such file or directory Makefile.rules:84: qvalue.d: No such file or directory Makefile.rules:84: re.d: No such file or directory Makefile.rules:84: receive.d: No such file or directory Makefile.rules:84: resolve.d: No such file or directory Makefile.rules:84: route.d: No such file or directory Makefile.rules:84: route_struct.d: No such file or directory Makefile.rules:84: script_cb.d: No such file or directory Makefile.rules:84: socket_info.d: No such file or directory Makefile.rules:84: sr_module.d: No such file or directory Makefile.rules:84: stats.d: No such file or directory Makefile.rules:84: tcp_main.d: No such file or directory Makefile.rules:84: tcp_read.d: No such file or directory Makefile.rules:84: timer.d: No such file or directory Makefile.rules:84: tsend.d: No such file or directory Makefile.rules:84: udp_server.d: No such file or directory Makefile.rules:84: unixsock_server.d: No such file or directory Makefile.rules:84: usr_avp.d: No such file or directory Makefile.rules:84: mem/f_malloc.d: No such file or directory Makefile.rules:84: mem/mem.d: No such file or directory Makefile.rules:84: mem/memtest.d: No such file or directory Makefile.rules:84: mem/q_malloc.d: No such file or directory Makefile.rules:84: mem/shm_mem.d: No such file or directory Makefile.rules:84: mem/vq_malloc.d: No such file or directory Makefile.rules:84: parser/hf.d: No such file or directory Makefile.rules:84: parser/msg_parser.d: No such file or directory Makefile.rules:84: parser/parse_allow.d: No such file or directory Makefile.rules:84: parser/parse_content.d: No such file or directory Makefile.rules:84: parser/parse_cseq.d: No such file or directory Makefile.rules:84: parser/parse_disposition.d: No such file or directory Makefile.rules:84: parser/parse_diversion.d: No such file or directory Makefile.rules:84: parser/parse_event.d: No such file or directory Makefile.rules:84: parser/parse_expires.d: No such file or directory Makefile.rules:84: parser/parse_fline.d: No such file or directory Makefile.rules:84: parser/parse_from.d: No such file or directory Makefile.rules:84: parser/parse_hname2.d: No such file or directory Makefile.rules:84: parser/parse_hostport.d: No such file or directory Makefile.rules:84: parser/parse_methods.d: No such file or directory Makefile.rules:84: parser/parse_nameaddr.d: No such file or directory Makefile.rules:84: parser/parse_param.d: No such file or directory Makefile.rules:84: parser/parse_rpid.d: No such file or directory Makefile.rules:84: parser/parse_rr.d: No such file or directory Makefile.rules:84: parser/parse_sipifmatch.d: No such file or directory Makefile.rules:84: parser/parse_to.d: No such file or directory Makefile.rules:84: parser/parse_uri.d: No such file or directory Makefile.rules:84: parser/parse_via.d: No such file or directory Makefile.rules:84: parser/parser_f.d: No such file or directory Makefile.rules:84: parser/digest/digest.d: No such file or directory Makefile.rules:84: parser/digest/digest_parser.d: No such file or directory Makefile.rules:84: parser/digest/param_parser.d: No such file or directory Makefile.rules:84: parser/contact/contact.d: No such file or directory Makefile.rules:84: parser/contact/parse_contact.d: No such file or directory Makefile.rules:84: db/db.d: No such file or directory Makefile.rules:84: db/db_fifo.d: No such file or directory Makefile.rules:84: lex.yy.d: No such file or directory Makefile.rules:84: cfg.tab.d: No such file or directory yacc -d -b cfg cfg.y conflicts: 1 shift/reduce make: *** [cfg.tab.c] Broken Pipe what could be the possible cause of these errors? How will i deal with it? Another question, does the ser-0.9.3 package for solaris support mysql, radius accounting and authentication? Thanks, -- Ryan Pagquil Infodyne Inc. - PhilOnline.com 3603 Antel Global Corporate Center Doña Julia Vargas Ave. Ortigas Center Pasig City Tel: 687-0715 Web: www.philonline.com

4 4

[Serusers] failure_route question
by Java Rockx 25 Aug '05

25 Aug '05

Hi All. I'm using t_check_status() to do call forwarding on 486 Busy responses. I have an odd thing happening where SER receives the 486 Busy message (for which SER properly sends an ACK response) and then the failure_route calls append_branch() and t_relay() to try another destination. After the new leg of the call is setup and then torn down, the original 486 Busy seems to be hung in the tm module, because it magically appears in ngrep, which shows it being sent back to the caller as if the append_branch() never took place. Is there anything special that I should be doing to "swallow" the 486 Busy response to prevent it from being sent to the caller UA? Regards, Paul

10 20

[Serusers] LCR Module - Does it support PSTN prefix digits?
by Paul Hazlett 21 Aug '05

21 Aug '05

Hi All. We have multiple PSTN gateways in our network. Some are our own and some are owned and operated by 3rd parties. We are also use ser-0.9 stable with the LCR module for call routing. Some of these 3rd party PSTN gateways require us to prefix accounting digits to the R-URI before sending the call to their network. So my questions is this; does the LCR module support a scenerio whereby it can prefix digits for specific PSTN gateways? For example, suppose I have 3 PSTN gateways. The the second gateway requires prefixed digits on the R-URI. When the fist GW fails, the LCR module would prefix the required digits and then send to the send GW. If the second GW fails, then the LCR module would remove the previously prefixed digits and then send the call to the 3rd GW. Is this possible is the LCR module Juha provides for ser-0.9 stable? If not, is it possible with the LCR module in the unstable CVS HEAD? Regards, Paul

3 4

[Serusers] Replication problem
by Andreas Granig 19 Aug '05

19 Aug '05

Hi all, we use DNSSRV balancing and forward_tcp() to replicate registrations from one SER to the other SERs in the system. Now when one machine completely crashes, all other SER processes on all other machines hang when processing a REGISTER until tcp-connect times out, leading to a system load of ~16 per machine assuming 16 child processes per SER, and no other messages can be processed. I understand that replicating using UDP would solve this issue, but then replicated registrations get lost every now and then because of unreliable transmission, and as far as I found out t_replicate() can only be used for replicating to *one* other SER. This really gets me thinking about patching out the internal location cache and lookup every location from memory, because this additional lookup really doesn't hurt because of ~10 other DB queries per call. IMHO in systems with more than two SERs this cache is just a big pain. Andy

5 21

[Serusers] ser_fifo
by Siphiwo Dzingwe 11 Aug '05

11 Aug '05

Hi I just installed ser v0.8.14 from the *.tar.gz distribution and when I try to run serctl moni it gives me an error saying: Error opening ser's FIFO /tmp/ser_fifo Make sure you have line fifo=/tmp/ser_fifo in your config in the ser.cfg file the line fifo="/tmp/ser_fifo" is uncommented. what am I doing wrong

2 1