[cisco-voip] SIP Binding: Different Binds for Carrier vs Internal

[Schlotterer, Tommy]

Yes,

You also will want to turn on Mode border-element under Voice service Voip

Address hiding is technically not needed as CUBE does this by default.

Thanks

Tommy

Tommy Schlotterer        |      Engineer

Presidio
         |      presidio.com<http://www.presidio.com/>

20 N Saint Clair 3rd Floor, Toledo, OH 43604
D: 419.214.1415<tel:419.214.1415>        |      C: 419.706.0259<tel:419.706.0259>        |      tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>



[https://www2.presidio.com/signatures/Presidio_Blue_FutureBuilt_200px.png]<http://www.presidio.com/>




From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Matthew Loraditch
Sent: Friday, September 11, 2020 3:25 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] SIP Binding: Different Binds for Carrier vs Internal

EXTERNAL EMAIL




I need to bind call legs to my carrier to one IP and all legs to CUCM on another IP on the same router and neither side ever see the other’s IP nor need to route to it

I’ve done something, at least similar, many years in the past but no longer have access to the environment to verify the behavior and am trying to refresh myself on the setting.

In that setup we bound the dial peers to the relevant interfaces and enabled allow-connections sip to sip and address-hiding in my voice service voip config.

From what I further understand media flow-through is the default behavior so as long as I do the binding, I will get what I want to happen happening.

Am I generally correct in all of my current thoughts? Anything I’m not thinking of?







Matthew Loraditch​

Sr. Network Engineer


p: 443.541.1518<tel:443.541.1518>



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>


[Helion Technologies]<http://www.heliontechnologies.com/>


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>










This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/41910a9f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6884 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/41910a9f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 431 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/41910a9f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/41910a9f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 444 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/41910a9f/attachment-0003.png>