What it sounds like you are trying to do to me, is allow the call to ultimately setup with a URI different than the URI that was dialed, without the calling party being the wiser.
DNS won’t be able to do anything with regards to that I don’t think, because it really sounds like you’re trying to manipulate/transform the called URI, and you’ll need something to interact with the SIP message stack for that I’d think. You can create a round robin A record, that resolves to multiple IP addresses, so when the client looks up the DNS SRV, it receives multiple targets to try before considering the SRV target “unreachable” (SRV weights and priorities determine the ordering of the target addresses resolved for the client). However, this won’t have the ability to change the called URI, which is ultimately what I think you’re attempting in the scenario (DNS and SIP messages are on different networking layers). As Dave mentioned below, Expressway or a LUA script (sip normalization) in CUCM seems to be uniquely qualified for what you’re wanting to do. Sent from my iPhone On Oct 4, 2019, at 20:40, Lelio Fulgenzi <le...@uoguelph.ca> wrote: I’ve seen some references to Cisco SIP proxy server. Would that help? -sent from mobile device- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1<x-apple-data-detectors://1/0> 519-824-4120 Ext. 56354<tel:519-824-4120;56354> | le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048077710&sdata=S%2BefDShYlkhoUCv8UWev6bGzWjLDFK0zeR8D6AybCCk%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] On Oct 4, 2019, at 7:46 PM, Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>> wrote: According to RFC 2782 (https://www.ietf.org/rfc/rfc2782.txt<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfc%2Frfc2782.txt&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048087715&sdata=IuzbX7iIL%2B701WKSoqOVA8jUKD2xWXx5ACgHIlyxvsI%3D&reserved=0>), it does not, under the “Target Definition”; “there must be one or more address records for this name, the name must not be an alias”. However, I can tell you that I have used a CNAME in the SRV target field before, and it appeared to work at the time. Still, depending on the application, doing so could potentially cause some weird issue with regards to PTR or something. Sent from my iPhone On Oct 4, 2019, at 19:10, Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>> wrote: I don't think DNS SRV records support CNAME. Even then, it would only change where it was sent to and not the SIP headers. On Fri, Oct 4, 2019 at 12:26 PM Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote: Yeah – I’d want this to happen all within DNS. But of course, in a supported fashion. I’m not interested in spending time modifying infrastructure at this time. I’ve done some searching, and there’s talk of RR records, but we haven’t found much documentation. --- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048097726&sdata=nq9QNHJ9%2F0%2Fx6MWj0warAw6sAdZy120eZOYLfOmLtYw%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook <image001.png> From: Dave Goodwin <dave.good...@december.net<mailto:dave.good...@december.net>> Sent: Friday, October 4, 2019 12:09 PM To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> Cc: cisco-voip voyp list <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] SIP Domain substitution Are you wanting this to all happen within DNS instead of happening within a SIP UA? As far as I understand, if DNS redirected somewhere (SRV or CNAME record for example) it would not change the destination URI the originator is trying to reach. The SIP protocol has redirection codes (such as 301 or 302) but whether or how you might be able to use them depends on the SIP UAs being used. You might also be able to use something like a SIP normalization script (CUCM), SIP profiles (CUBE), or maybe search pattern replacements (Expressway) to just translate the domain as calls flow in/out. I'm guessing what might be feasible without knowing more of the picture. On Fri, Oct 4, 2019 at 11:10 AM Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote: Does SIP allow for domain name substitution? By this I mean, instead of advertising or dialing coy...@phones.america.acmemanufacturing.com<mailto:coy...@phones.america.acmemanufacturing.com> I want to use coy...@zing.com<mailto:coy...@zing.com> But I don’t want to have to reorganize and reprogram anything. I just want the DNS to say, “hey, use this domain instead and try again.” -sent from mobile device- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354<tel:519-824-4120;56354> | le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048107731&sdata=93AEj4F8AXeCpjz39AddgIx9pvYqIFhmJ478P%2B6hzr4%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048117742&sdata=9GMpHxIfwWC%2F3QahTdR6EocxqFljdTdCV2VRdcwnlt4%3D&reserved=0> _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048127747&sdata=dJXXkn8NYYyVbpsshDE1y%2BXiPq6H4U%2BtiyT9XcX%2FPTc%3D&reserved=0> _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8490bfb695e94274db6d08d7491ffa5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058274001837045&sdata=zfbMgSZMo1JkN8aVUEQ0s%2B18Hgsoa9887UvQ3z1v6rw%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C8d67c4a26a104ee8d3e808d7492c8ff2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637058328048137758&sdata=PGe1zL7yCJocZ0K%2FU574O7soDCSGFxkXFnWU4Y3%2FYAI%3D&reserved=0>
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
