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

Jonathan Charles jonvoip at gmail.com
Fri Jan 12 15:33:35 EST 2018


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/20180112/6f60da89/attachment.html>


More information about the cisco-voip mailing list