Dave, I thought that but Expressway E rejects the call even before it sends it to Expressway C which in turns sends it to CUCM (pretty sure that’s how it works). I can’t find out why it gets a 404
Sent from my iPhone > On Mar 29, 2020, at 7:36 AM, Dave Wolgast <dwolg...@rochester.rr.com> wrote: > > > The most common reason for these in my experience is a missing or incorrect > inbound CSS on the sip trunk(s) between cloud & prem. > > > >> On Sun, Mar 29, 2020, 7:10 AM Mike O <mik...@msn.com> wrote: >> Hi All, >> >> I've racked my brain on this. I cannot get a call from the cloud to the on >> prem CUCM to work. On-prem to cloud works fine so I know Expressway to cloud >> TLS is working etc. I've attached a screen shot of the call leg from >> expressway -E where the call gets rejected with 404 not found. I can ping >> and resolve cluster1.domain.com (which is the pub). >> >> Thanks, >> Mike >> >> >> _______________________________________________ >> 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
