Oracle® WebLogic Communication Services Installation Guide 11g Release 1 (11.1.1) E13808-02 |
|
![]() Previous |
![]() Next |
This chapter describes post-installation steps for Oracle WebLogic Communication Services (OWLCS). It contains the following topics:
Section 6.2, "Provisioning Third-Party Call Control (TPCC) Users to Enable Third Party Call Control"
The out-of-the-box realm (example.com
) should be changed to reflect the realm or domain of your deployment. Make these modifications to the realm or domain:
SIP Container Domain Aliases setting
Login to Console. For example: http://weblogic.example.com:7001/console
Click the SipServer link on left navigation pane.
In the Configuration->General tab scroll down to Domain Aliases and enter the realm you want to choose (for example: yourdomain.com).
Alternatively, this change can be made by editing $DOMAIN_HOME/config/custom/sipserver.xml
Realm for Digest Identity Asserter
Login to the Console. For example: http://weblogic.example.com:7001/console
Click Security Realms on the left navigation pane.
Click myRealm.
Click the Providers tab.
Click DigestIdentityAsserter.
Click Provider Specific tab.
Scroll down to the DigestRealmName attribute and choose the appropriate realm (for example: yourdomain.com).
Alternatively, this change can be made by editing $DOMAIN_HOME/config/config.xml
Realm for Aggregation Proxy
Open JConsole:
-J-Djava.class.path=$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar:$WLS_HOME/lib/wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
where $WLS_HOME = $MW_HOME/wlserver_10.3/server/
$JAVA_HOME should point to JDK 1.6
jconsole -J-Djava.class.path=%JAVA_HOME%/lib/jconsole.jar;%JAVA_HOME%/lib/tools.jar;%WLS_HOME%/lib/wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
Once JConsole starts up, connect to the MBean Server using the following URI:
service:jmx:t3://<yourhost>:7001/jndi/weblogic.management.mbeanservers.domainruntime
Change the value of the following MBean attribute under AggregationProxy. Realm = <value>
For example: Realm = yourdomain.com
Alternatively, this change can be made by editing $MW_HOME/user_projects/domains/base_domain/Config/Communications/AggregationProxyServlet.xml
P-Asserted Identity URI for Third-Party Call Control
Open JConsole:
$JAVA_HOME/bin/jconsole -J-Djava.class.path=$JAVA_HOME/lib/jconsole.jar:$JAVA_HOME/lib/tools.jar:$WLS_HOME/lib/wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
where $WLS_HOME = $MW_HOME/wlserver_10.3/server/
$JAVA_HOME should point to JDK 1.6
jconsole -J-Djava.class.path=%JAVA_HOME%/lib/jconsole.jar;%JAVA_HOME%/lib/tools.jar;%WLS_HOME%/lib/wljmxclient.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote
Once JConsole starts up, connect to the MBean Server using the following URI:
service:jmx:t3://<yourhost>:7001/jndi/weblogic.management.mbeanservers.domainruntime
Change the value of the following MBean attribute under oracle.sdp.thirdpartycall -> ThirdpartyCall
for all server instances:
PAssertedIdentityURI: Replace domain (example.com) in default value of sip:tpcc.user@example.com
Alternatively, this change can be made by editing $MW_HOME/user_projects/domains/base_domain/Config/ThirdPartyCall.xml
Ensure that you restart all instances of the OWLCS servers after making the above configuration changes.
Authentication for INVITE
requests initiated by Third Party Call Control is accomplished by inserting a P-Asserted Identity Header in the request by the Third Party Call Control application. By default, the PAssertedIdentityURI
is set to sip:tpcc.user@example.com
; for authentication to be successful, you must create and provision the corresponding TPCC user. To create and provision the user:
Use Sash to issue the following command:
identity add privateId=tpcc.user publicId=sip:tpcc.user@example.com realm=example.com role="Location Service"
Enter a password of your choice when prompted (this password is not part of TPCC configuration, so an actual value is not used anywhere).
Ensure you replace example.com with the realm or domain for your installation. Third Party Call Control will not work if the above user is not created and provisioned.
Note: For more information on provisioning users and using Sash, see Oracle WebLogic Communication Services Administrator's Guide. |