Cisco Sip/2.0 500 Internal Server Error
Contents |
a 500 Internal Server Error
Sip Response 500 Internal Server Error
"Routing Failed" event is received. Error Message 500 Internal Server cisco cube sip/2.0 500 internal server error Error "Routing Failed". Possible Cause A SIP Trunk is not configured to receive or send calls sip/2.0 500 internal server error from cucm to the IP Address from the source of the SIP INVITE event. Recommended Action The solution is to configure a SIP Trunk to the IP address of the sending endpoint, CUPS, Gateway,
Sip 2.0 500 Server Internal Error Audiocodes
or Unified CVP. Release Release 7.0(2) Associated CDETS# None. Currently 4.13/512345 Rating: 4.1/5 (24 votes cast) Retrieved from "http://docwiki.cisco.com/wiki/SIP_Troubleshooting:_SIP_Calls_Receives_500_Internal_Server_Error_%22Routing_Failed%22_Event" Category: Unified CVP, Release 7.0(2) Views Page Leave a Comment View Source History Personal tools Log in Navigation Main Page Recent changes Random page Help Feedback Search Toolbox What links here Related changes Special pages Printable version Permanent link Print as PDF This page was last modified on 18 December 2009, at 19:07. This page has been accessed 34,188 times. © 1992-2015 Cisco Systems, Inc. All rights reserved. Trademarks Privacy policy About DocWiki Terms of Use
CollaborationCisco Unified Customer Voice PortalTroubleshoot and AlertsTroubleshooting TechNotes CVP "500 internal server error" Message Troubleshoot Download Print Available Languages Download Options PDF sip 2.0 500 internal server error lync (55.7 KB) View with Adobe Reader on a variety of devices sip 2.0 500 internal server error uc500 Updated:Sep 10, 2013 Document ID:116452 Contents Introduction Prerequisites Requirements Components Used Problem Verify Solution Introduction This document describes
Got Sip Response 500 Server Internal Error Back From
a problem encountered in Cisco Voice Portal (CVP) comprehensive call flow where a 500 internal server error is received, and a solution to the problem is given. Prerequisites Requirements http://docwiki.cisco.com/wiki/SIP_Troubleshooting:_SIP_Calls_Receives_500_Internal_Server_Error_%22Routing_Failed%22_Event Cisco recommends that you have knowledge of these topics: CVP Version 8.5 Intelligent Contact Manager (ICM) Components Used This document is not restricted to specific software and hardware versions. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If http://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-customer-voice-portal/116452-problemsolution-product-00.html your network is live, make sure that you understand the potential impact of any command. Problem In a CVP comprehensive call flow, a call is received on CVP,CVP sends a Session Initiation Protocol (SIP) INVITE to a third-party User Agent (UA), and the third-party UA rejects the INVITE with a 500 internal server error message. This problem only happens with CVP Version 8.5 and later. The caller hears a prompt message, then silence, and the call is disconnected. Here is an example of the call flow: The caller places a call from the Public Switched Telephone Network (PSTN). The Ingress Gateway (IGW) receives the call from the PSTN. The IGW sends an SIP INVITE message to CVP via an SIP proxy server. CVP sends a New Call request to the ICM. The ICM executes the routing script and sends a Voice Response Unit (VRU) label to CVP. CVP sends an SIP INVITE message via SIP proxy server to the Voice XML Gateway (VXML GW). The VXML GW executes the bootstrap script and sends an HT
IP isWhoisCalculatorTool PointsNewsNews tip?ForumsAll ForumsHot TopicsGalleryInfoHardwareAll FAQsSite FAQDSL FAQCable TechAboutcontactabout uscommunityISP FAQAdd ISPISP Ind. ForumsJoin Search similar:CircleNet [ONLY BRIEFLY] Downcouple voip questions[Asterisk] SIP http://www.dslreports.com/forum/r30437656-Config-Inbound-call-from-SIP-Provider-reply-with-147-SIP-2-0-500-Internal-Server URI calls between 2 Asterisk servers[Anveo] Anveo https://ciscomarketing.jiveon.com/docs/DOC-43727 Direct with OBIUC320 with Helios 2N Door PhoneSPA 3102 wont make outgoing VOIP calls via iiNet (Australia) Forums → Equipment Support → Hardware By Brand → Cisco → [Config] Inbound call 500 internal from SIP Provider reply with 147;SIP/2.0 500 Internal Server uniqs263 Share « WS-2924C-XL-EN config files • [Config] No access internet from Cisco 800 series » retrijoin:2015-11-251 edit retri Member 2015-Nov-25 6:47 am [Config] Inbound call from SIP Provider reply 500 internal server with 147;SIP/2.0 500 Internal ServerHello, I need to configure inbound calls from SIP provider to UC520 and then to CUCM 8.6.2The calls do no go through, when a trace is performed the SIP Trunk Provider says UC520 replying with "500 internal server error" in response to inbound call. I know about this article »supportforums.cisco.com/ ··· business and i include address of SIP provider in ACL CCA_SIP_SOURCE_GROUP_EXTERNAL, but SIP/2.0 500 Internal Server Error is still there.!!!!!!!!!!!!!!!!!voice source-group CCA_SIP_SOURCE_GROUP_CUE_CMEaccess-list 4translation-profile incoming SIP_Incoming//access-list 4 remark CCA_SIP_SOURCE_GROUP_ACL_INTERNALaccess-list 4 remark SDM_ACL Category=1access-list 4 permit 192.168.10.1access-list 4 permit 10.1.10.0 0.0.0.3access-list 4 permit 192.168.10.0 0.0.0.255access-list 4 permit 10.1.1.0 0.0.0.255\\//voice translation-profile SIP_Incoming translate called 411\\//voice translation-rule 411 rule 1 /^9\(.*\)/ /ABCD9\1/\\!!!!!!!!!!!!!!!!!voice source-group CCA_SI
turn JavaScript back on and reload this page. All Places > Developer > Collaboration > Call Control > Voice Gateway > Documents Currently Being Moderated CUBE: leg_disconnect leg_incoming = 500 Internal Server Error Version 1 Created by cdnadmin on Jan 24, 2014 9:29 PM. Last modified by cdnadmin on Jan 24, 2014 9:29 PM. This document was generated from CDN thread Created by: Travis May on 21-09-2010 05:00:57 AM 5350xmc5350-jk9su2_ivs-mz.151-2.T1.binCUBEIssuing any of the following results in "500 Internal Server Error" instead of "BYE". This behavior occurs regardless of CONNECT status. leg_disconnect leg_incoming leg_disconnect leg_incoming 10 leg_disconnect leg_incoming 16"500 Internal Server Error" is undesirable becuase it is inaccurate and the originating gateway does not terminate the PSTN leg upon receipt of the 500.Issuing the following results in "480 Temporarily unavailable", which simply proves the IOS is receiving the TCL command properly. leg_disconnect leg_incoming 18**** TCL CODE ****proc proc_setup_indication { } { leg proceeding leg_incoming leg alert leg_incoming -p 8 timer start named_timer 5 legDisconnect }proc proc_named_timer { } { leg disconnect leg_incoming}proc proc_disconnect_done { } { call close}proc fnEventHandler { } { puts "\n************* LEGIN EVENT: [infotag get evt_event] ********\n" switch [infotag get evt_event] { "ev_setup_indication" { proc_setup_indication } "ev_named_timer" { proc_named_timer } "ev_disconnect_done" { proc_disconnect_done } } }requiredversion 2.1set fsm(any_state,ev_any_event) "fnEventHandler,same_state"fsm define fsm SINGLESTATE******** TRACE RESULT *********Sep 21 05:20:44.090: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received: INVITE sip:8669218890@216.52.221.142:5060 SIP/2.0Via: SIP/2.0/UDP 216.52.221.144:5060;x-route-tag="cid:TCAST@216.52.221.144";branch=z9hG4bK5A1BAB2From: