Hi Bodgan Thank you for your help I had the following "now commented" statement in route[1] route[1] { xlog("L_INFO","rewritehostport to VOIP_GW:5060"); ## Removed On 1.36 25 03 08 ## sethostport("xx.xx.xx.xx:5060"); if (subst_uri('/(sip:.*);nat=yes/\1/')){ setbflag(6); }; if (isflagset(5)||isbflagset(6)) { route(3); } if (!t_relay()) { sl_reply_error(); }; exit; } I commented it out as you can see now I cant login either but I am getting these errors Forbidden and Unauthorized Another thing I would like to mention is that it worked with non TLS clients using the previous setups. Thx for your help so far. -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: Tuesday, March 25, 2008 1:02 PM To: Ali Jawad Cc: users(a)lists.openser.org Subject: Re: [OpenSER-Users] UA Cant Connect To TLS Hi Ali, The REGISTER gets to the server and it is processed by the routing script - your script tries to relay the request to another destination: Mar 19 12:04:42 [29280] DBG:tm:t_relay_to: new transaction fwd'ed I would say the problem is on the cfg script and not in TLS part. Regards, Bogdan Ali Jawad wrote: */ available) */ ------------------------------------------------------------------------ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Thanks for your help and interest Bogdan..I know you are busy..I know that my script is related to the GW forwarding but that is the only thing related RELAY that I do "With reference to your first replay" My config is http://pastebin.com/m45551815 -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: Wednesday, March 26, 2008 3:07 PM To: Ali Jawad Cc: users(a)lists.openser.org Subject: Re: [OpenSER-Users] UA Cant Connect To TLS Hi Ali, but the script you listed doesn't seam to be related to REGISTER processing....for a GW forwarding. Regards, Bogdan Ali Jawad wrote: destination: everything ------------------------------------------------------------------------ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.