Here is what I'm trying to achieve. My CUBE receives calls for hundreds of different NANP 10-digit numbers with pretty much every 3-digit area code in the US. Depending on which region (East Coast, Midwest, South, West Coast, etc.) the area code belongs to I need to send the call to a specific SIP IVR server. Configuring a dial-peer per area code is a pain! Instead, I want to try use external service, SIP server or DNS, to map area codes to specific IP.
For example, if SIP call comes to sip:4145551212@CUBE, I want CUBE to look up 414 via DNS or SIP Server and send call to sip:email@example.com.
sip:8475551212@CUBE should be sent to sip:firstname.lastname@example.org
The user portion of the SIP URI must remain as the original phone number 4145551212 or 8475551212. My first thought is to do:
voice dial-peer 1 voip
session target dns:$e$.domain.com
If a call comes for sip:4145551212@CUBE, then IOS will send DNS request for NAPTR record:
126.96.36.199.188.8.131.52.1.4.domain.com. IN NAPTR 100 10 "U" "E2U+sip" "!^.*$!sip:\email@example.com!"
DNS response would yeild firstname.lastname@example.org
The problem with this solution though is that I need to create a separate DNS record for every phone number. Is there any way to do just one DNS record per area code? I was thinking about using ENUM tables, but if I strip the 4145551212 to just 414 and do NAPTR lookup of 4.1.4.domain.com., I can get it resolved to sip:email@example.com, but I lose the original phone number, which I need to deliver to the SIP server.
Is my only solution to use some SIP server that can map 10 digit numbers based on area codes to specific IPs?
Am I overthinking this? If I do NAPTR DNS look up of 184.108.40.206.220.127.116.11.1.4.domain.com. and my NAPTR record is:
4.1.4.domain.com. IN NAPTR 100 10 "U" "E2U+sip" "!^(.*)$!sip:\firstname.lastname@example.org!" .
would it match this record and return sip:email@example.com ?
UPDATE: Yeah, looks like if I were to create a separate zone per area code, for example 4.1.4.domain.com., I could then do record * that translates to !^(.*)$!sip:\firstname.lastname@example.org! . My only issue now is to get BIND working with regexp replacement "\1". ISC BIND 9.9 doesn't seem to support it.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.