Uh, yeah, it's been a problem in 100% of the cases I've dealt with,
especially meraki based sd-wan solutions. to the point that meraki support
cannot fix their issue, and asked the customer to disable the full mesh
tunneling, in order for sip to work correctly. this is even after the
merakis
If your SD-WAN solution has packet duplication (aka 0 time failover) my
experience is that it tends to work well.
Other SD-WAN solutions may work better for VoIP if you can pin SIP/s RTP/sRTP
to one side or the other (active/passive over active/active).
Depending on the VoIP and SD-WAN
I didn’t notice anything different then from the regular wan
Kent
> On Dec 19, 2019, at 13:50, Fares Alsaafani wrote:
>
>
> Hi all,
>
> Did anyone came recently cross deploying or POC voice over SDWAN solution.
> I’m looking for thoughts , experiences , tests , things to avoid?
>
> Fares,
Hi all,
Did anyone came recently cross deploying or POC voice over SDWAN solution.
I’m looking for thoughts , experiences , tests , things to avoid?
Fares,
--
Best Regards
*FARES ALSAAFANI*
___
cisco-voip mailing list
cisco-voip@puck.nether.net
Call hits gateway, we do not see proper MGCP set up to CCM... I think the
issue is between gateway and ccm.
It isn't consistent... maybe 1 out of ever 6-7 calls.
Jonathan
On Thu, Dec 19, 2019 at 10:24 AM Ryan Huff wrote:
> Is this issue on the back of a TN port or anything like that? Have
Is this issue on the back of a TN port or anything like that? Have you engaged
the carrier?
Maybe the gateway is actually working just fine?
Sent from my iPhone
On Dec 19, 2019, at 11:01, Jonathan Charles wrote:
It is a T1 CAS and the controller is up with no errors it is 1977 over
It is a T1 CAS and the controller is up with no errors it is 1977
over there.
Jonathan
On Thu, Dec 19, 2019 at 3:03 AM daniele visaggio
wrote:
> can you do a "show isdn status" ?
>
> Is the t1 completely up?
>
> Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles <
>
can you do a "show isdn status" ?
Is the t1 completely up?
Il giorno gio 19 dic 2019 alle ore 03:14 Jonathan Charles
ha scritto:
> We rebooted the CCM cluster and the problem persisted...
>
> Traces show no sign of the call int he calllog...
>
>
>
> Jonathan
>
> On Wed, Dec 18, 2019 at 8:00 PM
