[cisco-voip] SIP Binding: Different Binds for Carrier vs Internal
Matthew Loraditch
MLoraditch at heliontechnologies.com
Fri Sep 11 19:35:06 EDT 2020
Yeah I thought about that, but not my area of strength nor something I anticipate needing us to know down the road. The binding stuff seems to be sufficient for my needs.
Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: Jason Aarons <scubajasona at gmail.com>
Sent: Friday, September 11, 2020 7:26 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com>
Cc: cisco-voip <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] SIP Binding: Different Binds for Carrier vs Internal
[EXTERNAL]
What is VRF?
On Fri, Sep 11, 2020, 3:25 PM Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
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>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/7244dd21/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image646304.png
Type: image/png
Size: 9409 bytes
Desc: image646304.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/7244dd21/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image532914.png
Type: image/png
Size: 431 bytes
Desc: image532914.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/7244dd21/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image882702.png
Type: image/png
Size: 561 bytes
Desc: image882702.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/7244dd21/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image732077.png
Type: image/png
Size: 444 bytes
Desc: image732077.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200911/7244dd21/attachment-0003.png>
More information about the cisco-voip
mailing list