Blogs

Check out the new content on the Cisco Developer Network reflecting the New & Enhanced features in Cisco Unified Communication Manager 9.1.

See the new 9.1 SIP Documentation ...Read More

 

The Unified Communications 9.0 Partner Bundle packages Cisco’s Collaboration application software for our Collaboration partner community to leverage for their internal lab or demonstration systems. The 9.0 version is now available for order. Learn More >> ...Read More

 

Silent Monitoring & Recording Partners:

Please review the latest updates to our supported device matrix here: http://developer.cisco.com/web/sip/wikidocs

Regards,

George Gary, Product Manager ...Read More

 

Developer Partners,

Cisco announces the availability of our 2012 Developer Partner presentations shared at CiscoLive San Diego.

Please log into the Cisco Developer Network using your Partner UserID to download this content.

Access these presentations here: http://developer.cisco.com/web/cdc/devforumpreso PARTNER LOGIN REQUIRED
...Read More

 

Developer Partners,

Cisco announces the availability of our 2012 Developer Partner presentations shared at CiscoLive London.

Please log into the Cisco Developer Network using your Partner UserID to download this content.

Access these presentations here: http://developer.cisco.com/web/cdc/devforumpreso PARTNER LOGIN REQUIRED
...Read More

 

Showing 1 - 5 of 21 results.
Items per Page 5
of 5
First Previous Last

Forums

« Back to SIP Trunk Questions

Cisco Call Recording Interface random error Reason: Q.850;cause=47

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Cisco Call Recording Interface random error Reason: Q.850;cause=47
Answer
11/26/12 8:51 PM
Hello,
One of our customers is having problem with Cisco Call Recording interface. Most of the calls getting recorded fine except in case of consulation transfer. In case of consulation transfer some calls (to the same extension) get recorded, other calls getting error Reason: Q.850;cause=47. Any suggestions, ideas?
 
Thanks
 
bad call Wireshark
Message Header
Via: SIP/2.0/UDP 10.32.60.12:5060;branch=z9hG4bK152da74fee0f0
From: "Rob Trefz Agent" ;tag=ae0b7800-6bc8-4225-972e-582b03635c76-44193253
To: ;tag=002f1860
Date: Mon, 19 Nov 2012 15:03:11 GMT
Call-ID: 3acde700-aa14a2f-c1cb-c3c200a@10.32.60.12
User-Agent: Cisco-CUCM8.0
Max-Forwards: 70
P-Preferred-Identity: "Rob Trefz Agent"
CSeq: 102 BYE
Reason: Q.850;cause=47
Content-Length: 0
 
Good Call Wireshark
 
Message Header
Via: SIP/2.0/UDP 10.32.60.12:5060;branch=z9hG4bK152b64154c8fe
From: "Rob Trefz Agent" ;tag=ae0b7800-6bc8-4225-972e-582b03635c76-44193217
To: ;tag=302d2e62
Date: Mon, 19 Nov 2012 14:56:44 GMT
Call-ID: 54226380-aa148ac-c1c1-c3c200a@10.32.60.12
User-Agent: Cisco-CUCM8.0
Max-Forwards: 70
P-Preferred-Identity: "Rob Trefz Agent"
CSeq: 102 BYE
Content-Length: 0
Flag

RE: Cisco Call Recording Interface random error Reason: Q.850;cause=47
Answer
11/26/12 9:40 PM as a reply to srinivas voora.
This kind of error is usually seen when a transcoder, MTP or similar media-path helper resource is either not configured or has run out of available instances.  Ensuring that DTMF signaling type and codec usage is unified and configured correctly may help reduce the need for such resources.
Flag

Collateral


No files available