Readme.b2b_connect
1b2b_connect application
2
3This application is a full back2back user agent (i.e. both signaling and
4media is handled by SEMS and each user agent, caller and callee, only
5see the SEMs IP address).
6Thus, the outgoing call is connected in B2BUA mode with media relay ('b2abua'),
7so technically the two legs are independent sip dialogs and media sessions.
8
9The outgoing calls (B leg) are optionally SIP authenticated, so for example,
10normal gateways can be used. The uac_auth module must be loaded for this
11to work. If the uac_auth module is not loaded, the outgoing calls are not
12authenticated.
13
14P-App-Param in the INVITE sent to SEMS contains information required
15to do the second call from SEMS to callee, together with the request URI.
16The request URI username part should contain the user to call, while the
17P-App-Param should contain the domain SEMS should add to the username,
18as well as credentials (if the outgoing call must be authenticated).
19
20Example for SER:
21R-URI: john@semsip:5070
22append_hf("P-App-Param: u=semsuser;d=ser.mydomain.com:5060;p=password\r\n");
23
24This will result in sems trying to set up a call to john@ser.mydomain.com:5060.
25If a 407 Authentication required is received, semsuser and 'password' will be
26used as credentials.
27
28If b2b_connect.conf parameter transparent_destination is set to true
29(default is false), then Request URI and To URI are passed to the second
30leg unaltered.
31
32Improvements are of course welcome as svn diff to the semsdev mailing
33list.
34