Protocol Error Unspecified
Contents |
CLASS Cause 1 Unallocated (unassigned) number - This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned). Cause
Protocol Error Unspecified 111 Reason
2 No route to specified transit network - This cause indicates that the equipment sending isdn disconnect cause codes this cause has received a request to route the call through a particular transit network which it does not recognize. The ss7 release cause codes equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network, while it does exist, does not serve the equipment that is sending
Normal Unspecified What Is The Problem
this cause. This cause is supported on a network dependent basis. Cause 3 No route to destination - This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network-dependent basis. Cause 4 Send special information tone - This cause indicates that the called party cannot be reached for reasons
Cause 127 Interworking Unspecified
that are of long term nature and that the special information tone should be returned to the calling party. Cause 5 Misdialed trunk prefix - No procedures specified for US networks. Cause 8 Preemption - This cause indicates that the call is being preempted. Cause 9 Preemption - Circuit reserved for reuse. This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange. Cause 16 Normal call clearing - This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network. Cause 17 User busy - This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy, it is noted that the user equipment is compatible with the call. Cause 18 No user responding - This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of tim
Contact Us Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network 5w56 service Management Remote Access Optical Networking Getting Started with LANs
Cause Code 41 Temporary Failure
IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS q.850 cause=127 text= interworking unspecified AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms https://www.dialogic.com/webhelp/MSP1010/10.2.3/WebHelp/MSP_DG/ISUP/Cause_Codes.htm Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid https://supportforums.cisco.com/discussion/9350711/isdn-bri-error-cause-i0x82ef-protocol-error-unspecified Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Doc
Wireless Network Live Optimization Question HOF protocol error unspecified? If this is your http://www.finetopix.com/showthread.php/20909-HOF-protocol-error-unspecified first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the http://www.cnes.com/causecodes.html register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Showing results 1 to cause code 1 of 1 Thread: HOF protocol error unspecified? Thread Tools Show Printable Version Subscribe to this Thread… 2011-07-26,12:29 PM #1 vci07 View Profile View Forum Posts Member Reputation: 64 Join Date 2010-01-29 Location under the sun! Posts 87 HOF protocol error unspecified? Hi Guys, Need help, i always encounter this protocol error unspecified message, handover failure protocol error unspecified. I am just new in GSM, what is the cause of it? I attached the messages, TEMS Thanks a lot Attached Files message HOF.txt (16.1 KB, 8 views) Share 2011-07-2612:29 PM # ADS Finetopix Circuit advertisement Join Date Always Location Advertising world Posts Many Quick Navigation Live Optimization Top Site Areas User Control Panel Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Forum Support Announcements RF Careers Requests Newcomers Section Library Discussions for Wireless Network Live Optimization Backhaul & Transmission Requests Softwares For Wireless Network News Drive Test TEMS_Investigation SwissQual NEMO Probe COUEI Network Planning ATOLL Transmission Planning AIRCOM PLANET TEMS_CellPlanner Mapping & Tools Post-Processing ACTIX TEMS_Discovery NEMO_Analyzer Assistant Aexio&Mcom Vendors Specific Equipment Ericsson 2G GSM/CDMA/... 3G UMTS/HSPA/... 4G LTE... Huawei 2G GSM/CDMA/... 3G UMTS/HSPA/... 4G LTE... Nokia 3G UMTS/HSPA/... 2G GSM/CDMA/... 4G LTE... Alcatel-Lucent Samsung 4G LTE... Miscellaneous Firm
Cause No. 2 - No route to specified transit network (national use) [Q.850] This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network. While it does exist. does not serve the equipment which is sending this cause. Cause No. 3 - No route to destination [Q.850] This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network dependent basis. Cause No. 4 - send special information tone [Q.850] This cause indicates that the called party cannot be reached for reasons that are of a long term nature and that the special information tone should be returned to the calling party. Cause No. 5 - misdialed trunk prefix (national use) [Q.850] This cause indicates the erroneous inclusion of a trunk prefix in the called party number. This number is to sniped from the dialed number being sent to the network by the customer premises equipment. Cause No. 6 - channel unacceptable [Q.850] This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call. Cause No. 7 - call awarded. being delivered in an established channel [Q.850] This cause indicates that the user has been awarded the incoming call and that the incoming call is being connected to a channel already established to that user for similar calls (e.g. packet-mode x.25 virtual calls). Cause No. 8 - preemption [Q.850] This cause indicates the call is being preempted. Cause No. 9 - preemption - circuit reserved for reuse [Q.850] This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange. Cause No. 10 - normal call clearing [Q.850] This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network. Cause No. 17 - user busy [Q.850] This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the