Brian, We got part of the solution figured out the port number had been changed in the callmanager to vcs sip trunk. So no it didn't get to vcs. The "gremlins" are still at work as that hasn't solved the whole issue.
I'll add the bits of the trace to the email train when I get connected. Regards Andy > On 26 Feb 2016, at 16:14, Brian Meade <[email protected]> wrote: > > So it doesn't show up in the search history on VCS at all? > > What is the 503 Service Unavailable in response to? The Invite sent to VCS > and 503 is sent by VCS? If so, what does the Invite look like? > >> On Fri, Feb 26, 2016 at 8:55 AM, Andy Carse <[email protected]> wrote: >> Ok, so this used to work but now in cucm logs I see 503 service unavailable. >> >> There are 3 mx200 g2 that are used for conferencing. >> >> They are trying to call an h323 end point out on the interweb. >> 123.123.123.123 >> >> So we have the users dial [email protected] >> >> We have a sip route pattern 123.123.123.123 which points to the vcs sip >> trunk. >> >> On the vcs we have a transform that >> Strips off the ip@ and points at the traversal zone. >> >> It apparently used to work, but now it doesn't get passed to vcs. Cucm shows >> 503 service unavailable. >> >> Everything looks ok, but I'm missing something.... >> >> Thanks in advance >> >> Regards Andy >> >> _______________________________________________ >> 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
