Hi Ellie, Thank you for the response. I'm using ENUM rules on BIND and I don't have it fully working yet, but it's resolving to the correct domain now.
OPTIONS sip:[email protected];user=phone SIP/2.0 From: <sip:[email protected]>;tag=gKgrZ1oLEpAy6AvtbdjYr.-dPR4PFRStTo: <sip:[email protected];user=phone> 07-05-2014 19:54:45.636 Debug stateful_proxy.cpp:2246: Translating URI 07-05-2014 19:54:45.636 Debug dnsresolver.cpp:141: Sending DNS NAPTR query for 1.0.0.4.4.4.4.5.5.5.1.iot1.com 07-05-2014 19:54:45.637 Debug enumservice.cpp:435: Got NAPTR record: 100 10 "E2U+SIP" "U" "!^.*$!sip:[email protected]!" 07-05-2014 19:54:45.637 Debug enumservice.cpp:70: Split regex into match=^.*$, replace=sip:[email protected] 07-05-2014 19:54:45.637 Debug enumservice.cpp:375: Enum lookup completes: sip:[email protected] 07-05-2014 19:54:45.637 Debug stateful_proxy.cpp:1808: Update request URI to sip:[email protected] 07-05-2014 19:54:45.637 Info stateful_proxy.cpp:1594: Route request to domain example.com Thank you, Alan On 5/7/14 11:30 AM, "Eleanor Merry" <[email protected]> wrote: >Hi Alan, > >You can use ENUM and SIP URIs in your case below. > >You will need an ENUM rule that rewrites the domain of numbers that >belong to DomainB, e.g. a jsonized version would be: >{ > "number_blocks" : [ > { > "name" : "Numbers in DomainB", > "prefix" : "15554444", > "regex" : "!(^.*$)!sip:\\1@DomainB!" > } >} > >Sprout receives an INVITE to "sip:+15554444001@DomainA". It pulls out >'+15554444001' from the SIP URI, does an ENUM lookup on the number to see >if the domain should be rewritten, finds the ENUM rule and rewrites >DomainA to DomainB. > >Ellie > > > >-----Original Message----- >From: Kwon, Alan [mailto:[email protected]] >Sent: 07 May 2014 16:58 >To: Eleanor Merry; [email protected] >Subject: Re: Tel URI > >Hi Ellie, > >The use case that I'm trying to test is a multi-domain use case. Let's >say user A (1-555-444-3001) belongs to DomainA and B (1-555-444-4001) >belongs to Domain B. When user A tries to reach out to user B, in the >Contacts, A only has B's telephone number. If I configure the devices to >use SIP URI, INVITE will be sent to "sip:+15554444001@DomainA" and since >B belongs to DomainB, it obviously won't reach B. > >That's the reason I'm configuring the devices to use Tel-URI. So that >Tel:+15554444001 would be translated by ENUM to sip:+15554444001@DomainB. >So, is this type of multi-domain use case not currently supported by >Clearwater? > >Thanks, >Alan > > > >On 5/7/14 10:42 AM, "Eleanor Merry" <[email protected]> wrote: > >>Hi Alan, >> >>We don't currently support Tel-URIs. >> >>While Clearwater does have function to support ENUM lookups for a TEL >>URI (INVITEs only), this function isn't tested as part of our QA (and >>so there may be issues with it). We're expecting to add support for TEL >>URIs in the future - in the meantime are you able to use SIP URIs? >> >>Clearwater also supports ENUM lookups for numbers embedded in a SIP URI. >> >>Ellie >> >>-----Original Message----- >>From: [email protected] >>[mailto:[email protected]] On Behalf Of >>Kwon, Alan >>Sent: 06 May 2014 23:13 >>To: [email protected] >>Subject: [Clearwater] Tel URI >> >>Hi, >> >>I know that in the WIKI >>(https://github.com/Metaswitch/clearwater-docs/wiki/SIP-Interface-Speci >>fic ations), it says Tel-URI is not supported, but I was under the >>impression that you simply can't use the Tel-URI as your public URI, >>but would be able to send a request out to a Tel-URI since there's a >>support for ENUM server. >> >>I tried it today and I'm receiving 416. >> >>OPTIONS tel:+15554443001 SIP/2.0 >>From: >><sip:[email protected]>;tag=sYys9XoDHolpvwEf7Jv2o9dQdDSP-Nbo >>To: <tel:+15554443001> >> >>SIP/2.0 416 Unsupported URI Scheme >>From: >><sip:[email protected]>;tag=sYys9XoDHolpvwEf7Jv2o9dQdDSP-Nbo >>To: <tel:+15554443001>;tag=z9hG4bKPjJqZHB7Oo3n7ITZ9BbVvlEpO5czHUA0y6 >> >>So, Tel-URI is not supported at all? Then, what's the ENUM server used >>for? >> >>Thanks, >>Alan >> >>_______________________________________________ >>Clearwater mailing list >>[email protected] >>http://lists.projectclearwater.org/listinfo/clearwater > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
