[CICD]Q931 Disconnect Cause Codes

Introduction

This document explains how to interpret Integrated Services Digital Network (ISDN) disconnect cause codes. The ISDN disconnect cause code appears in the debug isdn q931 command output, and indicates the reason for call disconnection.

Note: Activate the debug isdn q931 command for this exercise. Remember that the debug isdn q931 command generates a large volume of debugs. Refer to Important Information on Debug Commands for more information on the safe use of debugs.

Here is a sample output of the debug isdn q931 command. The output indicates the disconnect cause code for a failed ISDN call:

Calling#ping 10.10.10.2 
   Type escape sequence to abort. 
   Sending 5, 100-byte ICMP Echos to 10.10.10.2, timeout is 2 seconds: 
   20:52:14: ISDN BR0: TX -> SETUP pd = 8 callref = 0x2E 
   20:52:14: Bearer Capability i = 0x8890 
   20:52:14: Channel ID i = 0x83 20:52:14: Keypad Facility i = '5551111' 
   20:52:15: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0xAE 
   20:52:15: Channel ID i = 0x89

   20:52:16: ISDN BR0: RX <- PROGRESS pd = 8 callref = 0xAE 
   20:52:16: Progress Ind i = 0x8A81 - Call not end-to-end ISDN,
     may have in-band info 
   20:52:16: Signal i = 0x01 - Ring back tone on
   20:52:34: ISDN BR0: RX <- DISCONNECT pd = 8 callref = 0xAE 
   20:52:34: Cause i =0x829F08 - Normal,unspecified or Special intercept,
     call blocked group restriction     
   20:52:34: ISDN BR0: TX -> RELEASE pd = 8 callref = 0x2E 
   20:52:34: ISDN BR0: RX <- RELEASE_COMP pd = 8 callref = 0xAE

The 0x in the disconnect code indicates that the subsequent bytes are in hexadecimal format and are not part of the actual code. This table provides a breakdown of the code after you strip the 0x from the debug output:

Cause i = 0x829F08
Parsed Hex Bytes 82 9F 08
Description Cause Code Origination Point Disconnect Cause Code Optional Diagnostic field

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document is based on the devices in a specific lab environment. All of the devices in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Cause Code Origination Point

The first byte (most significant) after 0x indicates the point in the circuit path where the disconnect cause code appears. Consider the sample output in the Introduction section. 82 indicates that the call disconnects from the local telco switch. Here is a list of cause code origination points that help you interpret where the call disconnects from:

  • 80—the router
  • 81—the private network near the local user (possibly a local private branch exchange [PBX])
  • 82—the public network near the local user (local telco switch)
  • 83—the transit network (in the ISDN cloud)
  • 84—the public network near the remote user (remote telco switch)
  • 85—the private the network near the remote user (possibly a remote PBX)
  • 87—the international network
  • 8A—a network beyond the internetworking point

Disconnect Cause Code

The next byte (9F in the sample output) that follows the cause code origination point byte is the Disconnect Cause Code. This byte helps you to troubleshoot the disconnection.

Use this table to associate a Disconnect Cause Code (in Hex) and the Cause Description to determine the disconnect reason:

Hex Code Cause Description Additional Information
80 Normal Disconnect The call disconnects normally.
81 Unallocated or unassigned number The switch receives the ISDN number in the correct format. However, the number does not belong to destination equipment.
82 No route to specified network The ISDN exchange receives a request to route the call through an unrecognized intermediate network. This cause indicates that the equipment receives a request to route the call through a particular transit network. However, the equipment does not recognize the network. The equipment that sends this cause does not recognize the transit network due to one of these reasons: The transit network does not exist. The transit network exists, but does not serve the equipment that sends this cause. This cause is supported on a network-dependent basis.
83 No route to destination The call routes through an intermediate network that does not serve the destination address. This cause indicates that the called user is not reachable. A user is not reachable when the network used to route the call does not serve the required destination. This cause is supported on a network-dependent basis.
84 Send special information tone The remote number you dialed is not reachable. Check the number you dial. Verify if you need any prefixes to access the network. For example, you need to dial 9 for outbound calls through a PBX. Contact your telco/PBX administrator for details.
85 Misdialled trunk prefix. The remote number you dialed is not reachable. Check the number you dial. Verify if you need any prefixes to access the network. For example, you need to dial 9 for outbound calls through a PBX. Contact your telco/PBX administrator for details.
86 Channel unacceptable The service quality of the specified channel is insufficient to accept the connection. The call attempt fails because the channel is unusable. If you use a PBX, check the configuration of the PBX. For a PRI, find out how many channels your telco provides.
87 Call awarded and delivered in established channel The user assigns an incoming call that connects to an already established call channel. This cause indicates that the user receives an incoming call, which connects to a channel already in use for similar calls (for example, packet-mode X.25 virtual calls).
88 Preemption Your call is blocked. Calls are sometimes blocked if another call has a higher priority than your call. This situation is common with voice calls. Wait and call again later. If you use a PBX (or the remote site to which you connect uses a PBX), check the configuration of the PBX. If the condition persists, contact your telco.
89 Preemption, circuit reserved for re-use Your call is blocked. Calls are sometimes blocked if another call has a higher priority than your call. This situation is common with voice calls. Wait and call again later. If either side uses a PBX, check the configuration of the PBX. If the condition persists, contact your telco.
90 Normal call clearing Normal call clearing occurs. You do not need to perform any action. This cause indicates that the call disconnects because one of the users involved in the call has made a request to clear the call. Under normal situations, the network is not the source of this cause. If the call fails with this Disconnect Cause Code, the call most likely fails at a higher layer protocol such as PPP, authentication or idle timeout related issues. Verify the router configuration. Also, if you have requested a callback, the remote device disconnects the call, generates this code, and then calls you back.
91 User busy The called system acknowledges the connection request. However, the system cannot accept the call because all B-channels are in use. The user equipment is compatible with the call in this situation. Note: If you have multiple ISDN circuits, the telco can configure them in a “hunt-group”, in which calls switch to the next available circuit.
92 No user response The connection fails because the destination does not respond to the call. This cause indicates that a user does not respond to a call establishment message within the prescribed period. The user must respond with either an alert or connect indication according to ITU-T Q.931, when either timer T303 or T310 expires.
93 No answer from user The destination responds to the connection request but fails to complete the connection within the prescribed time. This cause indicates that a user has provided an alert indication, but has not provided a connect indication within a prescribed period. Q.931 procedures do not necessarily generate this cause. Internal network timers sometimes generate this cause. The problem is at the remote end of the connection.
94 Subscriber absent The remote device you attempt to reach is unavailable and is disconnected from the ISDN network. Contact the person responsible for that device.
95 Call rejected The destination is able to accept the call but rejects the call for an unknown reason. This cause indicates that the equipment that sends this cause does not want to accept this call. Note: The equipment is able to accept the call because the equipment that sends this cause is neither busy nor incompatible. However, the equipment rejects the call.
96 Number changed The ISDN number used to set up the call does not belong to a system. A caller receives this cause when the called party number is no longer assigned. You can optionally include the new called party number in the diagnostic field. If a network does not support this capability, the caller receives cause No. 81, unassigned (unallocated) number.
97 Redirection to new destination Your call is routed to a different ISDN number. Check the number you call. Also verify the PBX configuration (if you use PBX).
99 Exchange routing error Your call cannot be successfully routed to the remote party. Check the number you call. Also verify the PBX configuration (if you use PBX).
9A Non-selected user clearing The destination is able to accept the call. However, the destination rejects the call because the call is not assigned to a user.
9B Destination out of order The destination is not reachable because of an interface malfunction. In addition, a signaling message cannot be delivered. This condition can be temporary. However, the condition can last for an extended period in some cases. This cause indicates that a signaling message could not be delivered to the remote user. For example, a physical layer or data link layer fails at the remote user end, and the user equipment is off-line (turned off).
9C Invalid number format The connection fails because the destination address is in an unrecognizable format, or is incomplete. Verify whether the format of the number is correct. This includes any appropriate digits for a PBX, and long distance.
9D Facility rejected The network cannot provide the facility that the user requests.
9E Response to STATUS ENQUIRY The status message appears in direct response to the receipt of a status inquiry message.
9F Normal, unspecified This message reports the occurrence of a normal event when no standard cause applies. No action is required.
A1 Circuit out of order The call cannot go through due to some problem in the ISDN network.
A2 No channel available The connection fails because no appropriate channel is available to take the call.
A3 Destination unattainable The destination is not reachable through the Telco network. Contact the Telco.
A4 Out of order Some part of the network necessary to route the call is out of order. The destination is not reachable because of a network malfunction. The condition can last for an extended period. An immediate attempt to reconnect will probably fail. If you use a long distance carrier, try to use a Presubscribed Inter-exchange Carrier (PIC). For example, you can use a 10-10-xyz carrier. A PIC enables you to verify whether the problem lies with the long distance carrier.
A6 Network out of order The destination is not reachable because of a network malfunction. The condition can last for an extended period. An immediate attempt to reconnect will probably fail. If you use a long distance carrier, try to use a Presubscribed Inter-exchange Carrier (PIC). For example, you can use a 10-10-xyz carrier. A PIC enables you to verify whether the problem lies with the long distance carrier.
A7 Permanent frame mode connection out of service This message indicates that equipment failure probably terminates the permanent connection. If the problem persists, contact your telco
A8 Permanent frame mode connection operational This message occurs when the permanent connection is fully operational again after a termination. Equipment failure probably terminated the connection previously.
A9 Temporary failure An error occurs because of a network malfunction. Contact the telco if the problem persists.
AA Switching equipment congestion The destination is not reachable because of a temporary overload on the network switching equipment. Try again later.
AB Access information discarded The network cannot provide the access information that the user requests. This cause indicates that the network is unable to deliver access information to the remote user. For example, user-to-user information, low layer compatibility, high layer compatibility, or a sub-address as the diagnostic indicates. Note: You have the option to include the particular type of discarded access information in the diagnostic.
AC Requested channel not available The remote equipment cannot provide the channel that the user requests, due to an unknown reason. This problem is usually temporary.
AF Resources unavailable, unspecified The channel or service that the user requests is unavailable for an unknown reason. This problem is usually temporary.
B1 Quality of service (QoS) unavailable The network cannot provide the quality of service that the user requests. This issue can occur due to a subscription problem. This cause reports that the network cannot provide the QoS as defined in Recommendation X.213. For example, this cause code appears when the network cannot support throughput or transit delay.
B2 Requested facility not subscribed The remote equipment supports the supplementary service by subscription only. This cause indicates that the network cannot provide the supplementary service that the user requests. The user has probably not completed the necessary administrative arrangements with the supporting networks. The ISDN network can also return this cause code when a user makes a call attempt, but does not enter the SPIDs, or enters the SPIDs incorrectly. Ensure that your SPIDs are correct, or contact your telco to verify your SPIDs. Also verify the speed of the outgoing call that the ISDN network supports (56k or 64k).
B4 Outgoing calls barred There is some restriction on outgoing calls. The ISDN network does not allow you to make outgoing calls.
B5 Outgoing calls barred within CUG1 There is some restriction on outgoing calls. The ISDN network does not allow you to make outgoing calls.
B6 Incoming calls barred The ISDN network does not allow you to receive calls. Contact your telco.
B7 Incoming calls barred within CUG1 The ISDN network does not allow you to receive calls. Contact your telco.
B9 Bearer capability not authorized A subscription problem usually causes this issue. This cause indicates that the user requests a bearer capability that the equipment implements, but the user does not have the authorization to use the capability.
BA Bearer capability not presently available The network normally provides the bearer capability that the user requests. However, if the capability is unavailable currently, this cause appears. A temporary network problem or a subscription problem can cause this issue. If the incoming call is Analog (modem call), verify whether you have an ISDN incoming voice-modem under the PRI or BRI physical interface.
BF Service/option not available, unspecified The network or remote equipment cannot provide the service option that the user requests, due to an unspecified reason. A subscription problem can cause this issue.
C1 Bearer capability not implemented The network cannot provide the bearer capability that the user requests. Contact the telco to troubleshoot further.
C2 Channel type not implemented The network or the destination equipment does not support the channel type that the user requests.
C5 Requested facility not implemented The remote equipment does not support the supplementary service that the user requests.
C6 Only restricted digital info bearer capability available The network cannot provide unrestricted digital information bearer capability. This cause indicates that a device requests an unrestricted bearer service. However, the equipment only supports the restricted version of the bearer capability.
CF Service/option not implemented, unspecified The network or remote equipment cannot provide the service option that the user requests, due to an unspecified reason. A subscription problem can cause this issue.
D1 Invalid call reference value The remote equipment receives a call with a call reference that is not currently in use on the user-network interface.
D2 Identified channel does not exist The user requests the receiving equipment to use a channel that is not activate on the interface for calls. This cause indicates that the equipment receives a request to use an inactive channel on the interface for a call. For example, if a user subscribes to those channels on a primary rate interface numbered from 1 to 12 and the user equipment or the network attempts to assign a call to channels 13 through 23, this cause code appears.
D3 Suspended call exists, but call id does not The network receives a call resume request. The call resume request contains a Call Identify (ID) information element that indicates the call ID that represents a suspended call. This cause indicates that a user attempts to resume a call with a call ID which differs from the ID in use for any currently suspended call(s).
D4 Call id in use The network receives a call resume request. The call resume request contains a Call ID information element that indicates the resume request is for a suspended call. This cause indicates that the network receives a call suspend request. The call suspend request contains a call ID (including the null call ID). This ID is already in use for a suspended call within the domain of interfaces over which the call can be resumed.
D5 No call suspended The network receives a call resume request when there is no suspended call pending. You can resolve this transient error through successive call retries. This cause code indicates that the network receives a call resume request. The call resume request contains a call ID information element that currently does not indicate any suspended call within the domain interfaces over which calls can be resumed.
D6 Call with requested call id has been cleared This cause indicates that the network receives a call resume request. The call resume request contains a call ID information element that originally indicated a suspended call. However, either a network timeout or a remote user clears the suspended call.
D7 User not member of CUG1 Your call does not go through, probably due to one of these reasons: You dial an incorrect ISDN number. You request a service that you are not authorized to use (you have not subscribed to this service). The remote device is not authorized to use a service that you use. Check the number you call. If the problem persists, contact your telco.
D8 Incompatible destination This cause indicates an attempt to connect to non-ISDN equipment. For example, an analog line. This cause indicates that the equipment receives a request to establish a call that has a low layer compatibility, high layer compatibility, or other compatibility attributes (for example, data rate) that the equipment cannot accommodate. This code often appears when the calling device dials the wrong number, and reaches a non-ISDN device. Therefore, ensure that you dial the correct number. This cause can also occur when a a data call is made to a voice number, or a voice call is made to a number that only supports data. If the number is correct, check whether the telco has configured their switch incorrectly.
DA Non-existent CUG1 Your call does not go through, probably due to one of these reasons: You dial an incorrect ISDN number. You request a service that you are not authorized to use (you have not subscribed to this service). The remote device is not authorized to use a service that you use. Check the number you dial. If the problem persists, contact your telco.
DB Invalid transit network selection The device requests the ISDN exchange to route the call through an unrecognized intermediate network. This cause indicates that the ISDN exchange receives a transit network identification of an incorrect format. Annex C of ITU-T Q.931 provides this definition.
DF Invalid message, unspecified An invalid message appears with no standard cause. This problem usually occurs due to a D-channel error. If the error occurs systematically, report the error to your ISDN service provider.
E0 Mandatory IE missing The receiving equipment receives a message that does not include one of the mandatory information elements. This cause indicates that the equipment receives a message that does not contain an information element that is necessary for the equipment to process the message. This problem occurs due to a D-channel error. Ensure that you configure the switch type correctly. Upgrade your Cisco IOS® Software on the router to solve this issue. If the error occurs systematically, report the error to your ISDN service provider.
E1 Message type not implemented The receiving equipment receives an unrecognized message, because either the message type is invalid, or the equipment does not support the message type. A problem with the remote configuration or with the local D-channel causes this issue.
E2 Message not compatible with call state or not implemented The remote equipment receives an invalid message with no standard cause. This cause indicates that the equipment receives a message that is not permissible in the call state according to the procedures. This cause can also indicate that the equipment receives a STATUS message to indicate an incompatible call state. The issue occurs due to a D-channel error. If the error recurs, report the error to your ISDN service provider.
E3 IE not implemented The remote equipment receives a message that includes information elements that the equipment cannot recognize. This cause indicates that the equipment receives a message that includes information elements that the device cannot recognize. This problem can occur when the equipment does not define or implement the information element identifier. However, the message does not need to contain the information element in order for the equipment to process the message. This issue occurs due to a D-channel error. If the error recurs, report the error to your ISDN service provider.
E4 The remote equipment receives a message that includes invalid information in the information element. This cause indicates that the equipment receives an information element that is implemented, but one or more of the fields in the information element are coded differently. This issue occurs due to a D-channel error.
E5 Message not compatible with call state The remote equipment receives an expected message that does not correspond to the current state of the connection. This issue occurs due to a D-channel error.
E6 Recovery on time expiry Your call does not go through, probably because an error occurs. For example, a state synchronization error. Wait and try again later. If the problem persists, contact your ISDN service provider.
E7 Parameter not implemented Your call does not go through because the ISDN network does not support a service you need to use. Contact your ISDN service provider.
EF Protocol error, unspecified This cause indicates an unspecified D-channel error with no other standard cause.
FF Interworking, unspecified This cause indicates that an event occurs, but the network does not provide causes for the action. The precise problem is unknown.
?? Unknown Cause value The cause value is unknown.

1 CUG: Closed User Group is a facility in X.25 and ISDN networks that allows a called number to be available only to a limited number of other users (in a virtual private network). Contact your telco for more information.

Optional Diagnostic field

The last two hexadecimal digits (08 in the example) are optional. You do not commonly use these digits for diagnostic purposes. However, you can sometimes use this byte to furnish additional information for the Disconnect Cause Code. The debug isdn q931 output can sometimes contain these digits.

[WWB] Oh 365 ~

How to determine the connection of application

Start  “Task Manager”—click  “Processes”—select “PID” box in “view-select Colunms”

Find out the PID of the application

Input the command “ netstat –ano | findstr “PID”

—————— pac file ——–

function FindProxyForURL(url, host)

{

    url = url.toLowerCase();

    host = host.toLowerCase();

                //——————————————————-

                // Traffic should go via proxy

                //——————————————————-

                if (

                                shExpMatch(host, “163.44.159.68”) ||   //Entry for this VPS

                                shExpMatch(host, “*.kkmg.vip”) ||       //Entry for this VPS

                                )

                return “PROXY 127.0.0.1:1080”;

    // Default Traffic Forwarding

     return ” DIRECT “;

}

[CICD]Extension Mobility Error Codes

Extension Mobility Application Error Codes

Table 1 Extension Mobility Application Error Codes
Error Code Phone Display Quick Description Reason
201 Please try to login again (201) Authentication Error If the user is an EMCC user, this error can occur if “EMCC” is not activated on the Intercluster Service Profile window.
202 Please try to login again (202) Blank userid or pin The user enters a blank user ID or PIN.
204 Login is unavailable (204) Directory server error The EMApp sends this error to the phone when IMS could not authenticate the user with the given PIN.
205 Login is unavailable (205)

Logout is unavailable (205)

User Profile Absent Occurs when the user profile information cannot be retrieved from the cache or the database.
207 Login is unavailable(207)

Logout is unavailable(207)

Device Name Empty Occurs when the device or name tag is missing in the request URI. This cannot happen with real devices and can occur only if the request is sent from third-party applications.
208 Login is unavailable(208)

Logout is unavailable(208)

EMService Connection Error The visiting EMApp cannot connect to any Visiting EMService. (The service is down or not activated.)

The visiting EMService cannot connect to the Home EMService (the WAN is down or certificates are not trusted.)

210 Login is unavailable(210)

Logout is unavailable(210)

Init Fail-Contact Admin An error (such as a database connection failure) occurred while initializing EMApp. The error can occur because of a failure to connect to the database during startup.
211 Login is unavailable(211)

Logout is unavailable(211)

EMCC Not Activated Occurs when the PSTN is not activated in the Intercluster Service Profile window of the visiting cluster.
212 Login is unavailable(212) Cluster ID is invalid Occurs when a remote cluster update fails by sending an incorrect cluster ID to the remote cluster.
213 Login is unavailable(213)

Logout is unavailable(213)

Device does not support EMCC Occurs when a device does not support EMCC.

Extension Mobility Service Error Codes

Table 2 Extension Mobility Service Error Codes
Error Code Phone Display Quick Description Reason
0 Login is unavailable(0)

Logout is unavailable(0)

Unknown Error The EMService failed for an unknown reason.
1 Login is unavailable(1)

Logout is unavailable(1)

Error on parsing When the EMService cannot parse the XML request from the EMApp or EMService. This error occurs when third-party applications send an incorrect query to login XML (EM API). The error can also occur because of a version mismatch between home and visiting clusters.
2 Login is unavailable(2) EMCC Authentication Error The EMCC user credentials cannot be authenticated because the user entered an incorrect PIN.
3 Login is unavailable(3)

Logout is unavailable(3)

Invalid App User Invalid application user. This error commonly occurs because of the EM API.
4 Login is unavailable(4)

Logout is unavailable(4)

Policy Validation error The EM Service sends this error when it cannot validate the login or logout request because of an unknown reason, an error while querying the database or an error while retrieving information from the cache.
5 Login is unavailable(5)

Logout is unavailable(5)

Dev. logon disabled A user logs into a device that has Enable Extension Mobility unchecked in the Phone Configuration window.
6 Login is unavailable(6)

Logout is unavailable(6)

Database Error Whenever the database returns an exception while executing the query or stored procedure that the EM Service requests (login/logout or device/user query), the EM Service sends this error code to EMApp.
8 Login is unavailable(8)

Logout is unavailable(8)

Query type undetermined No valid query was sent to the EMService (DeviceUserQuery and UserDeviceQuery are valid ones). This error occurs because of the EM API or incorrect XML input.
9 Login is unavailable(9)

Logout is unavailable(9)

Dir. User Info Error This error appears in two cases:

  1. IMS returns an exception when it attempts to authenticate a user.
  2. When information about a user cannot be retrieved either from the cache or database.
10 Login is unavailable(10)

Logout is unavailable(10)

User lacks app proxy rights The user tries to log in on behalf of another user. By default, a CCMSysUser has administrative rights.
11 Login is unavailable(11)

Logout is unavailable(11)

Device Does not exist The phone record entry is absent in the device table.
12 Phone record entry is absent in the device table Dev. Profile not found No device profile is associated with the remote user.
18 Login is unavailable(18) Another user logged in Another user is already logged in on the phone.
19 Logout is unavailable(19) No user logged in The system attempted to log out a user who has not logged in. This error occurs when sending logout requests from third-party applications (EM API).
20 Login is unavailable(20)

Logout is unavailable(20)

Hoteling flag error Enable Extension Mobility is unchecked in the Phone Configuration window.
21 Login is unavailable(21)

Logout is unavailable(21)

Hoteling Status error The current user status was not retrieved from either the local cache or database.
22 Login is unavailable(22) Dev. logon disabled Occurs when EM is not enabled on device and the request is sent via EM API or when the services button is pressed on phone.
23 Login is Unavailable (23)

Logout is Unavailable (23)

User does not exist Occurs when the given user ID is not found (in any of the remote clusters).
25 Login is unavailable(25) User logged in elsewhere The user is currently logged in to some other phone.
26 Login is unavailable(26)

Logout is unavailable(26)

Busy, please try again Occurs when the EMService has currently reached the threshold level of Maximum Concurrent Requests service parameter.
28 Login is unavailable(28)

Logout is unavailable(28)

Untrusted IP Error Occurs when the Validate IP Address service parameter is set to True and the user tries to log in or log out from a machine whose IP address is not trusted. For example, a third-party application or EM API from a machine is not listed in the Trusted List of Ips service parameter.
29 Login is unavailable(29)

Logout is unavailable(29)

ris down-contact admin The Real-Time Information Server Data Collector (RISDC) cache is not created or initialized, and the EMService is unable to connect to RISDC.
30 Login is unavailable(30)

Logout is unavailable(30)

Proxy not allowed When login and logout occur through proxy (“Via” is set in HTTP header) and the Allow Proxy service parameter is set to False.
31 Login is unavailable(31)

Logout is unavailable(31)

EMCC Not Activated for the user Occurs when the Enable Extension Mobility Cross Cluster check box is not checked in the End User Configuration window of the home cluster.
32 Login is unavailable(32)

Logout is unavailable(32)

Device does not support EMCC Occurs when a device model does not have EMCC capability.
33 Login is unavailable(33)

Logout is unavailable(33)

No free EMCC dummy device Occurs when all the EMCC dummy devices are in use by other EMCC logins.
35 Login is unavailable(35)

Logout is unavailable(35)

Visiting Cluster Information is not present in Home Cluster Occurs when the home cluster does not have an entry for this visiting cluster.
36 Login is unavailable(36)

Logout is unavailable(36)

No Remote Cluster Occurs when the administrator has not added a remote cluster.
37 Login is Unavailable (37)

Logout is Unavailable (37)

Duplicate Device Name Occurs when the same device name exists in both the home cluster and visiting cluster.
38 Login is unavailable(38)

Logout is unavailable(38)

EMCC Not Allowed Occurs when the home cluster does not want to allow EMCC login (The Enable Extension Mobility Cross Cluster check box is not checked in the home cluster).
43 Login is unavailable(43) Device Security mode error The Device Security Profile that is associated to the EMCC device should be set to Nonsecure for its Device Security Mode.
45 Login is unsuccessful(45) Remote Cluster version not supported Occurs during EMCC login when the visiting cluster version is 9.x and is in mixed mode, the phone is in secure mode, and the home cluster version is 8.x.
46 Login is unsuccessful(46) Remote Cluster security mode not supported Occurs during EMCC login when the visiting cluster security mode is in mixed mode, the phone is in secure mode, and the home cluster is in nonsecure mode.

 

Read More…

[CICD] Wildcards and Special Characters in Translation Pattern

Character Description Examples
@ (@) 通配符匹配 所有 National Numbering Plan numbers.

每个 route pattern 只允许存在1个@ 通配符.

Route pattern ‘9.@’ 可以 routes 或者 blocks 所有 National Numbering Plan 可以识别的号码.

下列的 route patterns examples 显示了通配符 @ 包含的 National Numbering Plan numbers:

  • 0
  • 1411
  • 19725551234
  • 101028819725551234
  • 01133123456789
X (X)通配符表示匹配范围从0到9的任何单个数字 Route pattern ‘9XXX’ 可以 routes 或 blocks 范围从9000 到 9999的所有号码.
!  (!) 通配符表示匹配 范围从0到9的单个或任意多个数字. Route pattern ‘91!’ 可以routes 或 blocks 范围从 910 到 91999999999999999999999的所有号码.
? (?) 通配符表示匹配值的零个或多个的出现. Route pattern ‘91X?’ 可以 routes或blocks 范围从91 到 91999999999999999999999 的所有号码.
+  (+)通配符表示匹配值的一个或多个的出现. Route pattern ‘91X+’ 可以 routes 或 blocks 范围从 910 到 91999999999999999999999的所有号码.
[ ] ([ ]) 通配符表示匹配这几个数字内的一个. Route pattern ‘813510[012345]’ 可以 routes 或 blocks 范围从8135100 到 8135105的所有号码.
(-) 通配符与 方括号 一起使用,表示一个值的范围. Route pattern ‘813510[0-5]’ 可以 routes 或 blocks 范围从8135100 到 8135105 的所有号码.
^  (^) 通配符与 方括号 一起使用, 表示否定这一系列的值.

务必确保该通配符为方括号后的第一个字符 ([).

另外每个 route pattern 只允许有一个(^)通配符.

Route pattern ‘813510[^0-5]’ 可以 routes 或 blocks 范围从8135106 至8135109的所有号码.
. (.) 通配符,用作分隔符,多 用于在Cisco Unified Communications Manager(CUCM)从号码(directory number)区分出access code.

使用这个特殊通配符, 配合丢弃数字操作(discard digits),可以在 Cisco Unified Communications Manager(CUCM) 将号码发出前将 access code 剥离.

每个 route pattern 只允许有一个 (.) 通配符.

Route pattern ‘9.@’ 可以识别出 9 是一个 Cisco Unified Communications Manager 在National Numbering Plan 的一个 access code.
*  (*) 通配符可以为特殊拨号号码提供额外的数字. 可以配置route pattern ‘*411’ 可以拨打到任何号码的内部拨号.
#  (#) 通常表示拨号操作的结束.

确保# 通配符是位于这个pattern最后一个.

Route pattern ‘901181910555#’ 可以routes 或 blocks 从National Numbering Plan 的一个国际呼叫. 这里的 (#)通配符表示之前的(5)是呼叫队列中的最后一个数字.
\+ 反斜杠后的一个加号,就是(\+)通配符,表示你想要配置国际转义符+.

使用 (\+) 表示这里的 (+) 是国际转移符号用 可以拨打的,不是作为(+)通配符使用.

具体案例, 参考 Use the International Escape Character.

 

Read More…

WIFIpineapple 初始化流程

1、先将wifipineapple通过Y型USB连接电脑

IMG_0013

2、在浏览器地址栏中输入172.16.42.1:1471进行系统初始化操作

1-1

3、过程中可以选择wifi工作情况,之后也可以在相关配置页面修改

1-2

4、对配置页面登陆信息及管理用AP点进行设置

1-3

5、完成配置后,在宿主计算机上找到新增的适配器,可以重命名方便识别

1-4

6、共享一个宿主机可用的网络给wifipineapple

1-5

7、对wifipineapple的适配器添加相关IP地址

1-6

8、wifipineapple的管理页面 – route 确认相关设备连通性

1-7

 

9、我这里使用Xshell 连接设备

2-1

10、插件更新用地址加入hosts文件

2-2

11、如果有额外购买SD卡的进行fdisk分区操作

2-4

12、然后进行格式化

2-5

13、最后进行挂载操作

2-6

14、回到wifipineapple管理页面中的modules – 更新列表后得到可用列表一览

2-3

大致翻译如下

Module Version Description Author Size Type
SSLsplit 1  

Perform man-in-the-middle attacks using SSLsplit(使用SSLsplit执行中间人攻击)

whistlemaster 6.89kb GUI
DWall 1.1 Display’s HTTP URLs, Cookies, POST DATA, and images from browsing clients as a stream. Wall of Sheep style.(显示的HTTP url,cookie,POST数据和图像浏览客户流。) sebkinne 6.25kb GUI
Deauth 1.4 Deauthentication attacks of all devices connected to APs nearby(对附件AP连接的设备进行 解除身份验证 ) whistlemaster 7.21kb GUI
Evil Portal 2.1 An Evil Captive Portal. (一个邪恶的强制网络门户) newbi3 39.97kb GUI
nmap 1.4 GUI for security scanner nmap(nmap安全扫描的图形化界面) whistlemaster 6.27kb GUI
ettercap 1.4 Perform man-in-the-middle attacks using ettercap(使用ettercap执行中间人攻击) whistlemaster 8.27kb GUI
RandomRoll 1.1 This module allows you to troll unsuspecting clients connected to your WiFi Pineapple.(这个模块允许任意的用户端强制连接到这个wifipineapple) foxtrot 20403.63kb GUI
urlsnarf 1.4 Output all requested URLs sniffed from http traffic using urlsnarf(输出所有使用urlsnarf从http流量中嗅探出的url请求) whistlemaster 5.95kb GUI
Occupineapple 1.5 Broadcast spoofed WiFi SSIDs(广播虚假WiFi名称) whistlemaster 11.52kb GUI
Status 1.1 Display status information of the device(显示设备的状态信息) whistlemaster 43.56kb GUI
tcpdump 1.4 Dump traffic on network using tcpdump(使用tcpdump监听网络流量) whistlemaster 6.45kb GUI
DNSspoof 1.3 Forge replies to arbitrary DNS queries using DNSspoof(使用DNSspoof DNS回复任意DNS查询) whistlemaster 6.39kb GUI
Site Survey 1.2 WiFi site survey(调查无线网络环境) whistlemaster 10.23kb GUI
get 1.2 Profile clients through the browser plugins supported by their browser(配置客户端通过浏览器支持的浏览器插件) dustbyter 9.61kb GUI
Cabinet 1 A file manager for the Web Interface(一个Web界面的文件管理器) newbi3 3.10kb GUI
Online Hash Crack 1.1 Submit Hash and WPA Handshake to www.onlinehashcrack.com web service(提交哈希和WPA握手www.onlinehashcrack.com web服务) whistlemaster 4.91kb GUI
Log Manager 1.2 Manage all modules logs(管理所有模块日志) whistlemaster 2.95kb GUI
Papers 1.2 A TLS/SSL and SSH certificate generator/manager.(生成或管理 TLS / SSL和SSH证书) sud0nick 14.98kb GUI
p0f 1 Passive traffic fingerprinting using p0f(使用 p0f 进行静态流量监听) whistlemaster 5.92kb GUI
SignalStrength 1 Displays signal strength for wireless cells that are within range. Can be used to physically locate cells.(显示在范围内的无线单元的信号强度。可用于物理定位。) r3dfish 16.42kb GUI
ConnectedClients 1.4 Shows currently connected clients, DHCP leases and blacklist management.(显示当前连接的客户端,DHCP租约和黑名单管理。) r3dfish 2.14kb GUI
wps 1.2 WPS brute force attack using Reaver, Bully and Pixiewps(使用Reaver, Bully and Pixiewps进行暴力破解) whistlemaster 12.35kb GUI
Portal Auth 1 Captive portal cloner and payload distributor(网络划分及均衡负载) sud0nick 812.88kb GUI
ngrep 1.4 Match data part of packets on the network using ngrep(使用ngrep匹配数据网络上的数据包) whistlemaster 7.45kb GUI
autossh 1.2 Persistent SSH connections(持续的SSH连接) audibleblink 4.11kb GUI
Responder 1 LLMNR, NBT-NS and MDNS poisoner with built-in HTTP, SMB, MSSQL, FTP and LDAP rogue authentication server using Responder(使用应答器用LLMNR, NBT-NS MDNS 对 HTTP, SMB, MSSQL, FTP 和 LDAP进行解除身份验证) whistlemaster 80.75kb GUI
dump1090 1.1 Track aircraft ADS-B beacons with RTS-SDR using dump1090(使用dump1090跟踪带有 RST-SDR的 ADS-B信号) whistlemaster 6.48kb GUI
Key Manager 1 SSH Key Manager(SSH密钥管理器) whistlemaster 9.02kb GUI
LED Controller 1.1 This module allows you to control your LEDs.(这个模组能让你控制LED) foxtrot 42.19kb GUI
DNSMasq Spoof 1 Forge replies to arbitrary DNS queries using DNSMasq(使用DNSMasq DNS回复任意DNS查询) whistlemaster 4.88kb GUI
base64encdec 1 Base64 encoder and decoder(Base64编码器和译码器) dustbyter 2.12kb GUI
Module Maker 1 An easy way to generate modules.(方便生成模组) foxtrot 4.17kb GUI
API Tokens 1.1 Pineapple API Tokens Module(Pineapple API标记模块) tesla 2.23kb GUI
Commander 2 Control the Pineapple via IRC.(通过 IRC 控制Pineapple) foxtrot 3.87kb GUI

 

======   注   =========  意  ===========

2-7

部分插件与插件之间存在排斥关系,不可同时运行

 


更多关于wifipineapple厂商视频:

链接: https://pan.baidu.com/s/1hsnujyc

提取码: 6tc7

 

RAID5 阵列日常

NAS

听说 4块4T红盘 配战斧电源 = 泰坦配红星电源的效果!

===========================   大致的看图说话

这是丢失阵列次序的4块软RAID5硬盘,正在通过PE系统,模拟阵列丢失时的配置。

主要考虑了4种常规的循环方式 :左循环同步、左循环异步、右循环同步、右循环异步

并通过 diskgenius 对模拟数据进行了比对,但得出了如下完全不能理解的结果

2016-08-03-164928

我知道这看起来就是一个4的排列问题,但我还是排出了20种不同的组合方式

而且事实也证明这并没有什么用,到头来阵列还是被初始化,所有资料被重置 飞了

2016-07-14-163430