Mailing List Archive

So...are you still without a functional SIP trunk then Matt?

On Tue, Mar 31, 2020 at 8:08 AM Matthew Loraditch <
MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
> [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
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

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
w: www.heliontechnologies.com | e: MLoraditch@heliontechnologies.com
From: Anthony Holloway <avholloway+cisco-voip@gmail.com>
Sent: Wednesday, April 1, 2020 2:27 PM
To: Matthew Loraditch <MLoraditch@heliontechnologies.com>
Cc: cisco-voip@puck.nether.net
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 <MLoraditch@heliontechnologies.com<mailto:MLoraditch@heliontechnologies.com>> 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<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
|
e: MLoraditch@heliontechnologies.com<mailto:MLoraditch@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@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

Oh, good to hear!

Yeah NAT and SIP doesn't work without an ALG....well....sort of. You could
apply a Lua script to the SIP trunk to modify OUTBOUND INVITEs,
effectively doing your own SIP inspection, but then it would apply to all
CUCMs, and you'd need it to apply to only that one. Which you should be
able to do, but would require some reconfiguration of your SIP trunks, call
routing and callmanager groups.

Post back if you find a solution, or if you're still looking for help.

On Wed, Apr 1, 2020 at 1:29 PM Matthew Loraditch <
MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
> [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 <avholloway+cisco-voip@gmail.com>
> *Sent:* Wednesday, April 1, 2020 2:27 PM
> *To:* Matthew Loraditch <MLoraditch@heliontechnologies.com>
> *Cc:* cisco-voip@puck.nether.net
> *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 <
> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
>
> [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
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>

alguem te,sala cisco webex

Em qua., 1 de abr. de 2020 às 23:04, Anthony Holloway <
avholloway+cisco-voip@gmail.com> escreveu:

> Oh, good to hear!
>
> Yeah NAT and SIP doesn't work without an ALG....well....sort of. You
> could apply a Lua script to the SIP trunk to modify OUTBOUND INVITEs,
> effectively doing your own SIP inspection, but then it would apply to all
> CUCMs, and you'd need it to apply to only that one. Which you should be
> able to do, but would require some reconfiguration of your SIP trunks, call
> routing and callmanager groups.
>
> Post back if you find a solution, or if you're still looking for help.
>
> On Wed, Apr 1, 2020 at 1:29 PM Matthew Loraditch <
> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com*
>> <MLoraditch@heliontechnologies.com>
>> [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 <avholloway+cisco-voip@gmail.com>
>> *Sent:* Wednesday, April 1, 2020 2:27 PM
>> *To:* Matthew Loraditch <MLoraditch@heliontechnologies.com>
>> *Cc:* cisco-voip@puck.nether.net
>> *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 <
>> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com*
>> <MLoraditch@heliontechnologies.com>
>>
>> [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
>> 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
>

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 <
MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
> [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 <avholloway+cisco-voip@gmail.com>
> *Sent:* Wednesday, April 1, 2020 2:27 PM
> *To:* Matthew Loraditch <MLoraditch@heliontechnologies.com>
> *Cc:* cisco-voip@puck.nether.net
> *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 <
> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
>
> [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
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>

Outbound only

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________

Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch@heliontechnologies.com
From: Anthony Holloway <avholloway+cisco-voip@gmail.com>
Sent: Thursday, October 8, 2020 8:58:39 AM
To: Matthew Loraditch <MLoraditch@heliontechnologies.com>
Cc: cisco-voip@puck.nether.net <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] RedSky SIP Trunk


[EXTERNAL]


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 <MLoraditch@heliontechnologies.com<mailto:MLoraditch@heliontechnologies.com>> 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<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/> | e: MLoraditch@heliontechnologies.com<mailto:MLoraditch@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>

From: Anthony Holloway <avholloway+cisco-voip@gmail.com<mailto:avholloway%2Bcisco-voip@gmail.com>>
Sent: Wednesday, April 1, 2020 2:27 PM
To: Matthew Loraditch <MLoraditch@heliontechnologies.com<mailto:MLoraditch@heliontechnologies.com>>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
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 <MLoraditch@heliontechnologies.com<mailto:MLoraditch@heliontechnologies.com>> 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<tel:443.541.1518>

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

|

e: MLoraditch@heliontechnologies.com<mailto:MLoraditch@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@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

assuming that any potential call back goes to the DID, redsky is only
providing the address info and the call back number

On Thu, Oct 8, 2020 at 10:05 AM Matthew Loraditch <
MLoraditch@heliontechnologies.com> wrote:

> Outbound only
>
> Get Outlook for iOS <https://aka.ms/o0ukef>
>
> Matthew Loraditch?
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/> |
> e: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
> [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 <avholloway+cisco-voip@gmail.com>
> *Sent:* Thursday, October 8, 2020 8:58:39 AM
> *To:* Matthew Loraditch <MLoraditch@heliontechnologies.com>
> *Cc:* cisco-voip@puck.nether.net <cisco-voip@puck.nether.net>
> *Subject:* Re: [cisco-voip] RedSky SIP Trunk
>
>
> [EXTERNAL]
>
> 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 <
> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
> [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 <avholloway+cisco-voip@gmail.com>
> *Sent:* Wednesday, April 1, 2020 2:27 PM
> *To:* Matthew Loraditch <MLoraditch@heliontechnologies.com>
> *Cc:* cisco-voip@puck.nether.net
> *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 <
> MLoraditch@heliontechnologies.com> 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: *MLoraditch@heliontechnologies.com* <MLoraditch@heliontechnologies.com>
>
> [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
> 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
>