Was there a need for inbound traffic initiated from RedSky, or is this
purely outbound from CUCM?

On Wed, Apr 1, 2020 at 1:29 PM Matthew Loraditch <
[email protected]> wrote:

> Nope it is actually as simple as they said. Basic sip trunk out of CUCM.
> No special profiles, or anything.  Am having problems as one of my CUCMs
> goes through an ISR to get to RedSky vs an ASA. ISR NAT is being funky but
> dealing with that.
>
>
>
> Matthew Loraditch​
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
> e: *[email protected]* <[email protected]>
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
> [image: Facebook] <https://facebook.com/heliontech>
> [image: Twitter] <https://twitter.com/heliontech>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> *From:* Anthony Holloway <[email protected]>
> *Sent:* Wednesday, April 1, 2020 2:27 PM
> *To:* Matthew Loraditch <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: [cisco-voip] RedSky SIP Trunk
>
>
>
> [EXTERNAL]
>
>
>
> So...are you still without a functional SIP trunk then Matt?
>
>
>
> On Tue, Mar 31, 2020 at 8:08 AM Matthew Loraditch <
> [email protected]> wrote:
>
> Has anyone done this? Surprisingly they don’t provide a bunch of guidance
> here. I’m so used to carriers and other vendors being very very specific
> about how to setup their trunks.
>
>
>
> I was planning on doing them directly in CUCM as that seemed simpler, but
> would appreciate any input.
>
>
>
>
>
>
>
> *Matthew Loraditch**​*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *[email protected]* <[email protected]>
>
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to