That parameter is very useful to easily manage the cohabitation of a Polycom TCSPI integration and a SUT Lite implementation as illustrated in the schema below.
Today, I would like to present a new parameter: videoCallNumberMatcher
By default in the Sametime Phonebook, you have to different button when you want to initiate a call:
- Audio only Call
- Video Call
A new capability has been introduced to start a video call automatically when certain numbers are called. The solution IBM have implemented uses a client preference to control this behavior.
The client preference is a regular expression (using Java syntax) which is used to tested a called number to see is it a video device e.g. setting the preference to "60.*" would mean that when the user calls any number starting with 60 the client would know this is a video device. When the client detects the user is calling a video device, it will start a video call using the configured video provider rather than starting an audio call. That's exactly the same approach that sutLiteNumberMatcher uses.
So, if you have implemented sutLiteNumberMatcher, you can add a new line in your managed-setting xml file.The new managed-setting xml file will be similar than that:
<ManagedSettings>
<settingGroup name="com.ibm.collaboration.realtime.telephony.ui" lastModDate="20101008T101031Z">
<setting name="sutLiteNumberMatcher" value="60\d{3}" isLocked="false" />
<setting name="videoCallNumberMatcher" value="60\d{3}" isLocked="false" />
</settingGroup>
</ManagedSettings>
P.S: Open a service request with IBM Support to request a hotfix (#MEWE-8R4FD7) for IBM Sametime 8.5.2. IFR1 to leverage that parameter.
Great tip. Can you also change this expression so its not the number it starts with but the domain? Any calls to @video.xyz.com would also be video calls?
ReplyDeleteYes, you can use this regular expression "sip:.*@video.xyz.com" or ".*@video.xyz.com" instead of "60\d{3}". The SUTLitenumbermatcher uses any regex to recognize the SIP URI.
ReplyDelete