<div dir="ltr">Here is the VIA on the invite: <div><img src="cid:ii_160f10564fa14b23" alt="Inline image 1" width="471" height="158"><br></div><div><br></div><div>and the .103 under Telephony Group:</div><div><br></div><div><br></div><div><img src="cid:ii_160f10705e083e29" alt="Inline image 4" width="471" height="232"><br></div><div><br></div><div>Device is added under VoIP devices, it does show another ext as first in the list... I have verified the correct MAC and ext...</div><div><br></div><div>Weird thing is, sometimes we see no invite hit the CR server and the one time it appeared to work, the recording says, "recordingMonitorCallState.NoSIP"</div><div><br></div><div><br></div><div><br></div><div>I am starting to wonder if this works.</div><div><br></div><div><br></div><div>Jonathan</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 12, 2018 at 6:16 PM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Since you mentioned 7777, then I assume you meant QM and that in CUCM you have your Recording Destination Address in your Recording Profile set to 7777, correct?<br></div><div><br></div><div>So in QM, you don't program 7777 in anywhere. Just the fact that QM received the INVITE from your CUCMs which should all be in your Telephony group as Publisher/Subscribers, that should be it.</div><div><br></div><div>Check the Via: header IP on the INVITE from CUCM to QM, and make sure that IP is in the Telephony Group in QM.</div><div><br></div><div>Also while you're there, do you have the checkbox for enable network recording checked too?</div><div><br></div><div>And also while you're in the Admin tool, do you have a VoIP device configured for Network Recording too? And is that same device the one you put the recording profile on its line in CUCM and that you're testing with?<div><div class="h5"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 12, 2018 at 12:33 PM Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We are getting a 404 on inbound calls to the recorded destination from the QM CR in response to the CCM invite on the recording trunk... I am at a loss here. Is there a place to configure the recording pilot number (we are sending 7777 as our recording pilot to the SIP trunk...)</div><div dir="ltr"><div><br></div><div><br></div><div><br></div><div>Jonathan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 12, 2018 at 2:22 PM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I can't tell which direction you're referring to the 503 coming from, but in my experience CUCM will 503 you for two reason at least:<div><br></div><div>1) You didn't add the IP address which is sending to you, to a SIP trunk, so CUCM rejects the call</div><div><br></div><div>2) You need to bounce the SIP trunk again (and maybe even 3 or 4 more times just to be sure)</div><div><br></div><div>If you were meaning that QM sends the 503, it's possible QM is doing the same, and you are sending from a CUCM node that QM wasn't expecting to receive an INVITE from, or you just need to bounce the QM "sip trunk" which is probably one of the services I can't think of at the moment.</div></div><br><div class="gmail_quote"><div><div class="m_4307772748667031334m_8424474071300339307h5"><div dir="ltr">On Wed, Jan 10, 2018 at 8:58 PM Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_4307772748667031334m_8424474071300339307h5"><div dir="ltr">So, Built in bridge is enabled, sip trunk to Calabrio is set up... but when the call hits QM, we get a 503 Service Unavailable...<div><br></div><div>Not seeing a lot of documentation on what would cause this...</div><div><br></div><div>Any pointers to a direction?</div><div><br></div><div><br></div><div>Jonathan</div></div></div></div>
______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
</blockquote></div><br></div>
</blockquote></div></div></div></div></div>
</blockquote></div><br></div>