sr-users August 2005

sr-users@lists.kamailio.org

220 participants
558 discussions

[Serusers] Carrier-grade framework for SER

by Andreas Granig

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

18 years, 1 month

[Serusers] Modifying "From" header field of an INVITE message

by scm-j＠nuntius.com

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

18 years, 6 months

[Serusers] ser listening on multiple ports

by Iqbal

Hi Is it possible to get ser to listen on multiple ports at the same time iqbal

18 years, 7 months

RE: [Serusers] msilo, voicemail and serweb

by Alejandro Mellado

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

18 years, 10 months

Re: [Serusers] Distributing "OSP enable SER" binary file w/ source code

by vmathur＠transnexus.com

Hernan, OSP uses Public key based authentication and encrytion schemes, which are stronger than Radius's shared secrets. If you use OSP for authentication and authorization, you need not use Radius. OSP, just like Radius, has a client stack, which is implemented in the SER, and has a Server, which provides centralized call routing, accounting, and security. At the time of startup, the OSP server and the client, the SER in this case, exchange their public keys. The public and private keys can then be used to encode/decode messages as desired. A typical call setup procedure looks like this 1. The source SER goes to the osp server to get the SIP URI corresopnding to the destination. The message is encoded using the source SER's private key. 2. The osp server decodes the message using source SERs public key and after successful decoding (authentication) returns the route back to the source. Along with the route, it also sends back a digitally signed (using the OSP Servers private key) token. 3. The Source uses the route returned by the OSP Srver to send an INVITE. The INVITE message contains the token issued by the OSP Server 4. The destination decodes/validates the token using the OSP Servers public key. Upon successful validation (authorization) it accepts the call. This saves you the effort of mantaining cumbersome access lists for authentication. I can provide you with more documentatin on OSP and how to use SER with OSP if you wish Thanks, Vikrant ------------------------------------------------------------------------------------------------------------- Fogive my ignorance for I have never heard of OSP before ;) You mentioned Radius in your message. How does Radius authentication work in OSP? I am having a tough time getting mine to work. hernan vmathur(a)transnexus.com wrote: Dear All, I have recently implemented OSP w/ SER. OSP is an ETSI defined protocol, which I am using for ceneralised routing, and security of my inter-domain calls. The problem, however, is that the build process is a little lengthy. I want to contribute my implementation to this group so that anyone who is struggling with SER routing configurations or Radius authentication issues may benefit from it. I was, thus, wondering if we can have a binary file of the OSP enabled SER, that can be distributed with the source code. Does anyone have an opinion on this? Also, for anyone who wants to check-out this implementation, I can provide more details. Thanks, Vikrant _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

18 years, 10 months

[Serusers] Authenticate to Active Directory

by Bob McCormick

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?

18 years, 11 months

[Serusers] ser as outbound proxy only

by jeff kwong

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

18 years, 12 months

[Users] rport in via header

by ranveer kunal

hi all, Is there a way to configure openser so that it sends rport in via header ? Actually th packet from server is reverse natted through another system using any random port, i want it the reply to come on the same port . thanks .... Regards, Ranveer. -- Memories : They bring Diamonds and Rust

19 years

[Users] possibility to access dst_uri

by Daniel-Constantin Mierla

Hello, latest openser version from cvs includes a set of new functions (core and avpops) and pseudo-variable which allow to access and manage the value of dst_uri. The dst_uri field contains the address of the next hop, when the routing does not follow R-URI address. Such cases are Route header driven routing (dst_uri is set after loose_route() to the value of next Route header), contacts behind nat (dst_uri is set to the address of nat after lookup("location")) or dispatcher usage. The dst_uri has higher priority in routing over R-URI but less than explicit parameters in relaying functions (e.g., t_relay_to*()). The field was invisible from the script but it proved in the discussions on the mailing list to be important to access it. For example, to detect whether the caller and callee are behind same nat. Also, it can be checked in case of preloaded Route header to secure relaying to special resources (e.g., pstn gateway). With the new branch_route the value of dst_uri can be checked for each branch. A short summary of what was added: * core functions: - setdsturi("uri") - set the value of dst_uri - resetdsturi() - reset the value of dst_uri - isdsturiset() - test if the value of dst_uri is null * pseudo-variables - $du - value of dst_uri (added long time ago) - $dd - domain of dst_uri - $dp - port of dst_uri - $dP - transport protocol of dst_uri * avpops changes - avp_write() can read the value of dst_uri and write it in an avp - avp_pushto() can write the value of an avp in dst_uri Tutorials and dokuwiki will be updated soon. Daniel

19 years, 1 month

[Serusers] Solaris8/SPARC compilation

by Ryan Pagquil

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

19 years, 2 months

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 August 2005