Hi Eric, Thank you for your question.
A call between two different Clearwater deployments is an off-net call. Both have their own sets of subscribers so you can think of them as belonging to two different mobile operators. After you have configured<http://clearwater.readthedocs.io/en/stable/IBCF.html?#install-and-configure-an-ibcf> the IBCF with deployment B’s SIP trunk nodes you should use the BGCF to route calls to deployment B through this IBCF. In order to do this you would want a BGCF record like: { "routes" : [ { "name" : "Routing to B.ims", "domain" : "B.ims", "route" : [“sip:<ip of IBCF>:5060<sip:%3cip%20of%20IBCF%3e:5060>”] } ] } The BGCF rule you provided below would also attempt to route this call through deployment A, this would be an on-net call which doesn’t require a BGCF record. Once you have made this change run “sudo cw-upload_bgcf_json”. In terms of your ENUM configuration, an ENUM server is used to translate a telephone number you are calling in to a SIP URI. This means that it is not necessary if you are attempting to call a SIP URI (this is because the domain name would feature as part of the SIP URI already: sip:+1234@<deployment B>). If you are attempting to call a telephone number which is registered against deployment B you should use an ENUM rule to let the S-CSCF know to route the call off-net: *.4.3.2.1 IN NAPTR 1 1 "u" "E2U+sip" "!(^.*$)!sip:\\1@<deployment B>!" Once you have made this change run “sudo cw-upload_enum_json” You can read here<https://clearwater.readthedocs.io/en/stable/ENUM.html> for more information on how to configure ENUM. With these rules in place you shouldn’t require any additional DNS config. Could you please try making a call with the above BGCF/ENUM rules and let me know how it goes. If calls are still not being routed in the way in which you would expect, in addition to looking at wireshark traces you can also increase the detail of the logs which are recorded on your nodes. See here<http://clearwater.readthedocs.io/en/stable/Troubleshooting_and_Recovery.html?highlight=log_level> for details. Thanks, Andrew From: Clearwater [mailto:[email protected]] On Behalf Of ??? Sent: Tuesday, April 25, 2017 10:43 AM To: [email protected] Subject: [Project Clearwater] Call between two Clearwater Deployment Hi, I want to make a call between two clearwater deployment, and I found two configure guide as following : Multiple Domains http://clearwater.readthedocs.io/en/stable/Multiple_Domains.html?highlight=multiple%20domain Off-net Calling with BGCF and IBCF http://clearwater.readthedocs.io/en/stable/IBCF.html?highlight=IBCF I had following these step and set these configuration, and I make a call from clearwater deployment "A" to deployment "B". Finally, I got "Service Unavailable" message return. I installrf six component in a VM on VMware, and set IBCF and BGCF configuration in this VM. My configuration in "A" as following : /etc/clearwater/bgcf.json : { "routes" : [ { "name" : "Routing to B.ims", "domain" : "B.ims", "route" : ["sip:<ip of A>:5058<sip:%3cip%20of%20A%3e:5058>","sip:<ip of B>:5060<sip:%3cip%20of%20B%3e:5060>"] } ] } /etc/clearwater/user_settings : trusted_peers="<ip of B>" these are some questions about what cause fail: 1. Should I have to set ENUM configuration? I don't want to make off-net call, but external call between two clearwater deployment, just like IMS to IMS call. 2. I had check these SIP mes. transmission with wireshark, I found INVITE message did't pass to deployment B. 3.Should I set ibcf.a.ims in /etc/hosts file? or set in my dns file? Please give me some suggestions, I really want to successfully make a call between two deployment. Thanks, Eric
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
