Re: [cisco-voip] SIP Domain substitution

[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 have 
to permit) but a cloud registered device can call @myphone.acme.com

If I can create a macro on cloud registered devices like you can on CE devices, 
then it gives me that functionality.

We don’t have Webex Teams deployed. We don’t have Webex pstn / calling enabled.

So it’s either a hybrid call setup or a macro.

I’ll have to investigate further.

-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.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 11:25 PM, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

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 Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:

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 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

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 10:32 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone

On Oct 4, 2019, at 22:09, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:



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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto:le...@uoguelph.ca>> wrote:



I’ve seen some references to Cisco SIP proxy 

Re: [cisco-voip] SIP Domain substitution

[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.

 

On Fri, Oct 4, 2019 at 10:08 PM Ryan Huff mailto:ryanh...@outlook.com> > 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 mailto:avholloway%2bcisco-v...@gmail.com> > wrote:

 

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 mailto:natec...@gmail.com> > wrote:

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 mailto:ryanh...@outlook.com> > 
Sent: Friday, October 4, 2019 8:51 PM
To: NateCCIE mailto:natec...@gmail.com> >
Cc: Lelio Fulgenzi mailto:le...@uoguelph.ca> >; cisco-voip 
voyp list mailto:cisco-voip@puck.nether.net> >
Subject: Re: [cisco-voip] SIP Domain substitution

 

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 codec, 
using a non cloud uri (...@rooms.webex.com  ), and 
for that Webex Hybrid calling with Expressway B2B would get you there, and also 
checks the “no additional transformation needed” box.

 

Sent from my iPhone

 

On Oct 4, 2019, at 22:41, NateCCIE mailto:natec...@gmail.com> > wrote:

 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 does a quick trans to foo@internal.local  

 

 

Sent from my iPhone

 

On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi mailto:le...@uoguelph.ca> > wrote:

 

 

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.ca 
 

 

www.uoguelph.ca/ccs 

  | @UofGCCS on Instagram, Twitter and Facebook

 




On Oct 4, 2019, at 10:32 PM, Ryan Huff mailto:ryanh...@outlook.com> > wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

 

It’s a little bit of an ugly trombone, but it does work..

 

Sent from my iPhone

 

On Oct 4, 2019, at 22:09, Lelio Fulgenzi mailto:le...@uoguelph.ca> > wrote:

 

 

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 of Guelph

Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1

519-824-4120 Ext. 56354   | le...@uoguelph.ca 
 

 

www.uoguelph.ca/ccs 

Re: [cisco-voip] SIP Domain substitution

[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:
>
> 
> 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:
>
>> 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:* Lelio Fulgenzi ; cisco-voip voyp list <
>> cisco-voip@puck.nether.net>
>> *Subject:* Re: [cisco-voip] SIP Domain substitution
>>
>>
>>
>> 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
>> codec, using a non cloud uri (...@rooms.webex.com), and for that Webex
>> Hybrid calling with Expressway B2B would get you there, and also checks the
>> “no additional transformation needed” box.
>>
>>
>>
>> Sent from my iPhone
>>
>>
>>
>> On Oct 4, 2019, at 22:41, NateCCIE  wrote:
>>
>>  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 does a quick trans to foo@internal.local
>>
>>
>>
>>
>>
>> Sent from my iPhone
>>
>>
>>
>> On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi  wrote:
>>
>> 
>>
>>
>>
>> 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 <519-824-4120;56354> | le...@uoguelph.ca
>>
>>
>>
>> www.uoguelph.ca/ccs
>> 
>>  |
>> @UofGCCS on Instagram, Twitter and Facebook
>>
>>
>>
>> [image: University of Guelph Cornerstone with Improve Life tagline]
>>
>>
>> On Oct 4, 2019, at 10:32 PM, Ryan Huff  wrote:
>>
>> 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 normal, and
>> assuming the Hybrid integration was setup correctly, ring the Webex remote
>> destination which rings the cloud registered codec.
>>
>>
>>
>> It’s a little bit of an ugly trombone, but it does work..
>>
>>
>>
>> Sent from my iPhone
>>
>>
>>
>> On Oct 4, 2019, at 22:09, Lelio Fulgenzi  wrote:
>>
>> 
>>
>>
>>
>> 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 of Guelph
>>
>> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
>> N1G 2W1
>>
>> 519-824-4120 Ext. 56354 <519-824-4120;56354> | le...@uoguelph.ca
>>
>>
>>
>> www.uoguelph.ca/ccs
>> 
>>  |
>> @UofGCCS on Instagram, Twitter and Facebook
>>
>>

Re: [cisco-voip] SIP Domain substitution

[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 iPhone

On Oct 4, 2019, at 22:57, NateCCIE  wrote:


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: Lelio Fulgenzi ; cisco-voip voyp list 

Subject: Re: [cisco-voip] SIP Domain substitution

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 codec, 
using a non cloud uri (...@rooms.webex.com), and 
for that Webex Hybrid calling with Expressway B2B would get you there, and also 
checks the “no additional transformation needed” box.

Sent from my iPhone


On Oct 4, 2019, at 22:41, NateCCIE 
mailto:natec...@gmail.com>> wrote:
 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 does a quick trans to 
foo@internal.local


Sent from my iPhone


On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:


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.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 10:32 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone


On Oct 4, 2019, at 22:09, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:


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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
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 

Re: [cisco-voip] SIP Domain substitution

[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:

> 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:* Lelio Fulgenzi ; cisco-voip voyp list <
> cisco-voip@puck.nether.net>
> *Subject:* Re: [cisco-voip] SIP Domain substitution
>
>
>
> 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
> codec, using a non cloud uri (...@rooms.webex.com), and for that Webex
> Hybrid calling with Expressway B2B would get you there, and also checks the
> “no additional transformation needed” box.
>
>
>
> Sent from my iPhone
>
>
>
> On Oct 4, 2019, at 22:41, NateCCIE  wrote:
>
>  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 does a quick trans to foo@internal.local
>
>
>
>
>
> Sent from my iPhone
>
>
>
> On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi  wrote:
>
> 
>
>
>
> 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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> 
>  |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
> On Oct 4, 2019, at 10:32 PM, Ryan Huff  wrote:
>
> 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 normal, and assuming
> the Hybrid integration was setup correctly, ring the Webex remote
> destination which rings the cloud registered codec.
>
>
>
> It’s a little bit of an ugly trombone, but it does work..
>
>
>
> Sent from my iPhone
>
>
>
> On Oct 4, 2019, at 22:09, Lelio Fulgenzi  wrote:
>
> 
>
>
>
> 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 of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> 
>  |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
> On Oct 4, 2019, at 9:05 PM, Ryan Huff  wrote:
>
> 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 

Re: [cisco-voip] SIP Domain substitution

[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 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

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 10:32 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone

On Oct 4, 2019, at 22:09, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:



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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto: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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 

Re: [cisco-voip] SIP Domain substitution

[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: Lelio Fulgenzi ; cisco-voip voyp list 

Subject: Re: [cisco-voip] SIP Domain substitution

 

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 codec, 
using a non cloud uri (...@rooms.webex.com  ), and 
for that Webex Hybrid calling with Expressway B2B would get you there, and also 
checks the “no additional transformation needed” box.

 

Sent from my iPhone





On Oct 4, 2019, at 22:41, NateCCIE mailto:natec...@gmail.com> > wrote:

 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 does a quick trans to 
foo@internal.local  

 

 

Sent from my iPhone





On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi mailto:le...@uoguelph.ca> > wrote:

 

 

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.ca 
 

 

www.uoguelph.ca/ccs 

  | @UofGCCS on Instagram, Twitter and Facebook

 




On Oct 4, 2019, at 10:32 PM, Ryan Huff mailto:ryanh...@outlook.com> > wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

 

It’s a little bit of an ugly trombone, but it does work..

 

Sent from my iPhone





On Oct 4, 2019, at 22:09, Lelio Fulgenzi mailto:le...@uoguelph.ca> > wrote:

 

 

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 of Guelph

Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 
 

519-824-4120 Ext. 56354   | le...@uoguelph.ca 
 

 

www.uoguelph.ca/ccs 

  | @UofGCCS on Instagram, Twitter and Facebook

 




On Oct 4, 2019, at 9:05 PM, Ryan Huff mailto:ryanh...@outlook.com> > wrote:

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 mailto:le...@uoguelph.ca> > wrote:

 

Re: [cisco-voip] SIP Domain substitution

[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 codec, 
using a non cloud uri (...@rooms.webex.com), and for that Webex Hybrid calling 
with Expressway B2B would get you there, and also checks the “no additional 
transformation needed” box.

Sent from my iPhone

On Oct 4, 2019, at 22:41, NateCCIE  wrote:

 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 
does a quick trans to foo@internal.local


Sent from my iPhone

On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi  wrote:



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.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 10:32 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone

On Oct 4, 2019, at 22:09, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:



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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto: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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

Re: [cisco-voip] SIP Domain substitution

[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 
does a quick trans to foo@internal.local


Sent from my iPhone

> On Oct 4, 2019, at 8:36 PM, Lelio Fulgenzi  wrote:
> 
> 
> 
> 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.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> 
> 
>> On Oct 4, 2019, at 10:32 PM, Ryan Huff  wrote:
>> 
>> 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 normal, and assuming 
>> the Hybrid integration was setup correctly, ring the Webex remote 
>> destination which rings the cloud registered codec.
>> 
>> It’s a little bit of an ugly trombone, but it does work..
>> 
>> Sent from my iPhone
>> 
>>> On Oct 4, 2019, at 22:09, Lelio Fulgenzi  wrote:
>>> 
>>> 
>>> 
>>> 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 of Guelph
>>> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
>>> 2W1
>>> 519-824-4120 Ext. 56354 | le...@uoguelph.ca
>>>  
>>> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>>>  
>>> 
>>> 
>>> On Oct 4, 2019, at 9:05 PM, Ryan Huff  wrote:
>>> 
 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  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
> 519-824-4120 Ext. 56354 | le...@uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> 
> 
> On Oct 4, 2019, at 7:46 PM, Ryan Huff  wrote:
> 
>> 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 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  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  
 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.
 
  
 

Re: [cisco-voip] SIP Domain substitution

[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.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 10:32 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone

On Oct 4, 2019, at 22:09, Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:



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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto: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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 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, 

Re: [cisco-voip] SIP Domain substitution

[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 normal, and assuming the 
Hybrid integration was setup correctly, ring the Webex remote destination which 
rings the cloud registered codec.

It’s a little bit of an ugly trombone, but it does work..

Sent from my iPhone

On Oct 4, 2019, at 22:09, Lelio Fulgenzi  wrote:



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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto: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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 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 
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

Re: [cisco-voip] SIP Domain substitution

[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 of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 
2W1
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 9:05 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 
mailto: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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 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 
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

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook



From: Dave Goodwin mailto:dave.good...@december.net>>
Sent: Friday, October 4, 2019 12:09 PM
To: Lelio Fulgenzi mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list 
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 

Re: [cisco-voip] SIP Domain substitution

[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 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  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
519-824-4120 Ext. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 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 
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

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook



From: Dave Goodwin mailto:dave.good...@december.net>>
Sent: Friday, October 4, 2019 12:09 PM
To: Lelio Fulgenzi mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list 
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 
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

Re: [cisco-voip] SIP Domain substitution

[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. 56354 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

On Oct 4, 2019, at 7:46 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

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 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 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 
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

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook



From: Dave Goodwin mailto:dave.good...@december.net>>
Sent: Friday, October 4, 2019 12:09 PM
To: Lelio Fulgenzi mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list 
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 
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
 I want to use 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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net

Re: [cisco-voip] SIP Domain substitution

[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 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  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 
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

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook



From: Dave Goodwin mailto:dave.good...@december.net>>
Sent: Friday, October 4, 2019 12:09 PM
To: Lelio Fulgenzi mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list 
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 
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
 I want to use 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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs
 | @UofGCCS on Instagram, Twitter and Facebook

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voipdata=02%7C01%7C%7C8490bfb695e94274db6d08d7491ffa5a%7C84df9e7fe9f640afb435%7C1%7C0%7C637058274001837045sdata=zfbMgSZMo1JkN8aVUEQ0s%2B18Hgsoa9887UvQ3z1v6rw%3Dreserved=0
___
cisco-voip mailing list
cisco-voip@puck.nether.net

Re: [cisco-voip] SIP Domain substitution

[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 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
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* Dave Goodwin 
> *Sent:* Friday, October 4, 2019 12:09 PM
> *To:* Lelio Fulgenzi 
> *Cc:* cisco-voip voyp list 
> *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  wrote:
>
>
>
> 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 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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP Domain substitution

[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 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

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Dave Goodwin 
Sent: Friday, October 4, 2019 12:09 PM
To: Lelio Fulgenzi 
Cc: cisco-voip voyp list 
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 
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
 I want to use 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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] SIP Domain substitution

[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
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  wrote:

>
> 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 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 <519-824-4120;56354> | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] SIP Domain substitution

[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 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 | 
le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip