Sure Juan, I am currently working on a document that details how to compile OSP with SER, and also a white paper which tells you about the benefits of using OSP with SER. It should be ready soon :) and will send it across. In the meantime if you want to learn more about OSP, you can go to www.transnexus.com. By the way, we have also recently implemented OSP for use with the Asterisk PBX. So, if anyone here wants to use OSP for routing, security, or billing with Asterisk, let me know and I can provide more details. Thanks, Vikrant ---------------------------------------------------------------------- Hi Vikrant. It seems very interesting to me. I would like you to send me the info you have. Regards Juan ------------------------------------------------------------ From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of vmathur(a)transnexus.com Sent: Friday, August 12, 2005 11:00 AM To: hernan_gomez_1(a)yahoo.com Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Distributing "OSP enable SER" binary file w/ source code 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