h1. Goal (short description)

Routing of inter domain sessions over a TLS encrypted link between a SER and an OpenSER proxy 

h1. Applicability

Inter-domain SIP routing over TLS

h1. Prerequisites (OS, dependencies on other software)

Both proxies should have TLS enabled between itself and connected UAs. 

SER proxy: see

OpenSER proxy: see

h1. OS specific help

In /usr/local/etc/openser/openser.cfg, add routing to the other domain:
\\

        # check for requests targeted out of our domain
        if (\!uri==myself) {
                # mark routing logic in request
                append_hf("P-hint: outbound\r\n");
                # if you have some interdomain connections via TLS
                if(uri=~"@sipx1.ces.net")~ {                         t_relay("tls:sipx1.ces.net:5061");                         xlog("L_INFO", "Time \[%Tf\] Route to ces.net :%rm RURI:%ru  FROM:%fu TO:%tu \n buffer %mb \n flags \n %mf \n");                         exit;                 }else if(uri="@sipx.ten.cz")
{ t_relay("tls:sipx.ten.cz:5061");                         xlog("L_INFO", "Time \[%Tf\] Route to ten.cz :%rm                         RURI:%ru FROM:%fu TO:%tu \n buffer %mb \n flags \n                         %mf \n"); exit;                 }
                route(1);
\\

        };

h1. Validation, confirmation tests

In MS Windows Messenger 5.1 choose:

Tools \->

Options \->

Accounts tab \->

enable 'my contacts include users of a SIP communications service' and fill in under 'sign-in name:' <username>@<domain>

0 comments \| Add Comment