[cisco-voip] QM Call recording, getting 503 on inbound call recording call

[Jonathan Charles]

Here is the VIA on the invite:
[image: Inline image 1]

and the .103 under Telephony Group:


[image: Inline image 4]

Device is added under VoIP devices, it does show another ext as first in
the list... I have verified the correct MAC and ext...

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"



I am starting to wonder if this works.


Jonathan





On Fri, Jan 12, 2018 at 6:16 PM, Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> 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?
>
> 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.
>
> Check the Via: header IP on the INVITE from CUCM to QM, and make sure that
> IP is in the Telephony Group in QM.
>
> Also while you're there, do you have the checkbox for enable network
> recording checked too?
>
> 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?
>
>
> On Fri, Jan 12, 2018 at 12:33 PM Jonathan Charles <jonvoip at gmail.com>
> wrote:
>
>> 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...)
>>
>>
>>
>> Jonathan
>>
>> On Fri, Jan 12, 2018 at 2:22 PM, Anthony Holloway <
>> avholloway+cisco-voip at gmail.com> wrote:
>>
>>> 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:
>>>
>>> 1) You didn't add the IP address which is sending to you, to a SIP
>>> trunk, so CUCM rejects the call
>>>
>>> 2) You need to bounce the SIP trunk again (and maybe even 3 or 4 more
>>> times just to be sure)
>>>
>>> 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.
>>>
>>> On Wed, Jan 10, 2018 at 8:58 PM Jonathan Charles <jonvoip at gmail.com>
>>> wrote:
>>>
>>>> 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...
>>>>
>>>> Not seeing a lot of documentation on what would cause this...
>>>>
>>>> Any pointers to a direction?
>>>>
>>>>
>>>> Jonathan
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180113/81b4669c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 41629 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180113/81b4669c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 62083 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180113/81b4669c/attachment-0001.png>