Hi, in answer to your questions:
“So what is a suitable TAS…” We don’t recommend a TAS to integrate with an MRF, but (as you point out) the docs at http://clearwater.readthedocs.io/en/latest/SIP_Interface_Specifications.html#mrfc-control-rfc-4240-rfc-5552-rfc-6230-rfc-6231-rfc-6505 should hopefully give you what you need to establish whether a TAS will work. (As those docs say, all 3 methods of controlling the function of an MRFC from an AS are transparent to proxy components, and so all 3 are supported by Clearwater). “Is it confirmed that the built-in MMTEL AS cannot integrate directly with an MRF?” Correct, the built-in MMTEL AS is Project Clearwater cannot integrate directly with an MRF. Hope this helps, Seb. From: Clearwater [mailto:[email protected]] On Behalf Of Marcello 300sx Sent: 05 December 2016 15:20 To: [email protected] Subject: Re: [Project Clearwater] Clearwater Integration with MRF Hi Sebastian, thank you very much for your clarification. At this point I'd have other related questions by answering to your reply: 1) Project Clearwater doesn’t integrate directly with an MRF, but you can configure an AS that can control the MRF, and we’ve successfully integrated with MRFs via an AS in the past. --> So what is a suitable TAS to integrate a RFC and 3GPP MRF for Clearwater Rapidash release ? if it is Telestax Restcomm Media Server, are the following docs and softwares valid for Clearwater release yet? https://github.com/RestComm/mediaserver http://telestax.com/wp-content/uploads/2013/12/ClearWater-RestComm-Integration-2013.pdf - - > Definitively, can I consider the following requirements in order to integrate a MRF with Clearwater and AS? (coming from Clearwater documentation): MRFC control (RFC 4240<http://www.ietf.org/rfc/rfc4240.txt>, RFC 5552<http://www.ietf.org/rfc/rfc5552.txt>, RFC 6230<http://www.ietf.org/rfc/rfc6230.txt>, RFC 6231<http://www.ietf.org/rfc/rfc6231.txt>, RFC 6505<http://www.ietf.org/rfc/rfc6505.txt>) * These RFCs define three different ways of controlling the function of an MRFC from an AS. RFC 4240<http://www.ietf.org/rfc/rfc4240.txt> is a simple “play an announcement” service, RFC 5552<http://www.ietf.org/rfc/rfc5552.txt> uses VoiceXML and RFC 6230<http://www.ietf.org/rfc/rfc6230.txt>/RFC 6231<http://www.ietf.org/rfc/rfc6231.txt>/RFC 6505<http://www.ietf.org/rfc/rfc6505.txt> use SIP/SDP to establish a two-way control channel between the AS and MRFC. * IMS allows any of the three mechanisms to be used, or combinations depending on circumstances. * All three mechanisms are transparent to proxy components, so supported by Clearwater. 2) b. No, the built-in MMTEL TAS is not necessary. It will be installed on the Sprout node, but you don’t need to configure any calls to use it. --> so it is confirmed with Clearwater Rapidash Built-in MMTEL AS cannot be configured to integrate a MRF, isn't it ? Thank you very much for your availability! Have a nice day, /Marcello
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
