Hi Alan, If you can set up ENUM rules for numbers you know belong to your domain (or to other known domains), then you can set up a default rule in ENUM that will rewrite all other numbers, e.g.:
* IN NAPTR 1 1 "u" "E2U+sip" "!(^.*$)!sip:\\1@<your domain>!" Note however that when adding the rule to BIND the non-wildcard children of a wild-card domain are not themselves wildcarded, so you'll need to add in extra rules dependant on what number block belong to your domain. The example ENUM rules in our wiki give an example of using a default rule - please see https://github.com/Metaswitch/clearwater-docs/wiki/ENUM#bind. Hope this helps, Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kwon, Alan Sent: 20 November 2014 22:25 To: [email protected] Subject: [Clearwater] Interworking over IPX Hi, I would like to get some information on how to setup Clearwater for interworking to other domains over IPX (GSMA IR.90). I have previously setup 2 domains (cwims.com and example.com) and was able to interconnect them by setting up ENUM, IBCF, and BGCF. However, in that setup, each domain had explicit knowledge of the other, through bgcf.json and trusted_peers settings. Let's say "sip:[email protected];user=phone" INVITEs "sip:[email protected];user=phone" for a conversation, where B belongs to example.com domain. From what I understand, Sprout will do ENUM lookup on all addresses in home domain and will translate the terminating address to "sip:[email protected]". Now, if example.com is specified in bgcf.json, it'll get routed to the specified trunk. What I'm trying to setup is to setup a trunk to IPX and route all terminating endpoints that does not belong to my domain. So, in the scenario above, ENUM lookup on B would fail as I wouldn't have ENUM entries for all numbers for other operators... for these, I want them to be routed to a hub in IPX. Is this possible to setup something like this with Clearwater config or would this have to be done through an Application Server? Thank you, Alan _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
