Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
I’m trying to do a bit of everything, really. In our case, I’d like to have a few cloud registered WebEx room devices still be able to call our extensions. It’s the one thing we loose vs. on-prem reg WebEx room devices. I still have to get it working (I’m guessing there are IP address ranges I

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread NateCCIE
I didn’t see any reference to cloud registered… I should stop looking at my email tonight. From: Anthony Holloway Sent: Friday, October 4, 2019 9:11 PM To: Ryan Huff Cc: NateCCIE ; cisco-voip voyp list Subject: Re: [cisco-voip] SIP Domain substitution On a Friday night no less. O

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Anthony Holloway
Wait, I thought this was for other businesses to call you. Are you saying that to call within your own cloud you have to dial that giant URI? Is there no directory, or extension dialing? Clearly, I have not done a single Webex calling deployment yet. On Fri, Oct 4, 2019 at 10:06 PM Lelio Fulgen

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Anthony Holloway
On a Friday night no less. On Fri, Oct 4, 2019 at 10:08 PM Ryan Huff wrote: > Come on... we are geeks here we are going to run this down every > possible avenue regardless :) > > Sent from my iPhone > > On Oct 4, 2019, at 23:06, Anthony Holloway < > avholloway+cisco-v...@gmail.com> wrote: >

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
Come on... we are geeks here we are going to run this down every possible avenue regardless :) Sent from my iPhone On Oct 4, 2019, at 23:06, Anthony Holloway wrote:  I think Lelio was wondering about a pure cloud registered device, and then simply purchasing a vanity domain to overlay

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
Right... but the codec is registered in the Webex cloud (in this scenario), so you need to share the uri with the hybrid remote destination to trombone the call back out to the cloud if you’re letting the call come all the way into CUCM, and do it in a “least amount of MACD way”. Sent from my i

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Anthony Holloway
I think Lelio was wondering about a pure cloud registered device, and then simply purchasing a vanity domain to overlay on top of the ugly webex one. You knowlike URL shortening . On Fri, Oct 4, 2019 at 9:57 PM NateCCIE wrote: > Doe

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
Ok. Looking at it from the other way around, could I create a macro(?) on the cloud registered devices that ask for a 5 digit extension and then add the appropriate SIP domain to the extension to place the call? -sent from mobile device- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Comm

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread NateCCIE
Doesn’t cucm have the ability to look at the user portion of the URI only? For like when you’re routing to a DN? Or I think you can add the short domain to the list of the CUCM “owned” domains in enterprise parameters. From: Ryan Huff Sent: Friday, October 4, 2019 8:51 PM To: NateCCIE Cc

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
Hey Nate ... the original ask I think, was to do it all with DNS only and no intervention at layer 4, which to my knowledge, DNS alone couldn’t do. Expressway search rule, CUCM LUA script... etc could all do it in reality. However, the actual goal appears to be dialing a Webex cloud registered c

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread NateCCIE
I am not thinking right? Can’t a dns srv get the call routed to a specific host? Then a quick expressway transform to change the domain, and you’re done. Think of it as a different internal domain va external domain. f...@company.com does goes to expressway.companyinfrastructuredomain.com which

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
Interesting. I’ll have to look into that. Thx. -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 | le...@uoguelph.

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
Webex Hybrid Calling (with Expressway B2B), could in theory, help accomplish this. The codec is still cloud registered, though Hybrid calling would allow for an on-prem URI to be associated with the Webex remote destination of the codec. The call would come into the on-prem URI via B2B like nor

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
Darn. Double darn. Let’s hope webex offers up custom domain registration for devices soon. ‘Cause room...@acme.rooms.webex.com is a bit much. -sent from mobile device- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
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

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
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 519-824-4120 Ext. 5

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Ryan Huff
According to RFC 2782 (https://www.ietf.org/rfc/rfc2782.txt), 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

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Brian Meade
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 wrote: > Yeah – I’d want this to happen all within DNS. But of course, in a > supported fashion. I’m not interested in spendi

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
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

Re: [cisco-voip] SIP Domain substitution

2019-10-04 Thread Dave Goodwin
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

[cisco-voip] SIP Domain substitution

2019-10-04 Thread Lelio Fulgenzi
Does SIP allow for domain name substitution? By this I mean, instead of advertising or dialing coy...@phones.america.acmemanufacturing.com I want to use coy...@zing.com But I don’t want to have to reorganize and reprog