Asterisk variable Hangupcause

/* Causes for disconnection (from Q.931) */

1. define AST_CAUSE_UNALLOCATED 1
2. define AST_CAUSE_NO_ROUTE_TRANSIT_NET 2
3. define AST_CAUSE_NO_ROUTE_DESTINATION 3
4. define AST_CAUSE_CHANNEL_UNACCEPTABLE 6
5. define AST_CAUSE_CALL_AWARDED_DELIVERED 7
6. define AST_CAUSE_NORMAL_CLEARING 16
7. define AST_CAUSE_USER_BUSY 17
8. define AST_CAUSE_NO_USER_RESPONSE 18
9. define AST_CAUSE_NO_ANSWER 19
10. define AST_CAUSE_CALL_REJECTED 21
11. define AST_CAUSE_NUMBER_CHANGED 22
12. define AST_CAUSE_DESTINATION_OUT_OF_ORDER 27
13. define AST_CAUSE_INVALID_NUMBER_FORMAT 28
14. define AST_CAUSE_FACILITY_REJECTED 29
15. define AST_CAUSE_RESPONSE_TO_STATUS_ENQUIRY 30
16. define AST_CAUSE_NORMAL_UNSPECIFIED 31
17. define AST_CAUSE_NORMAL_CIRCUIT_CONGESTION 34
18. define AST_CAUSE_NETWORK_OUT_OF_ORDER 38
19. define AST_CAUSE_NORMAL_TEMPORARY_FAILURE 41
20. define AST_CAUSE_SWITCH_CONGESTION 42
21. define AST_CAUSE_ACCESS_INFO_DISCARDED 43
22. define AST_CAUSE_REQUESTED_CHAN_UNAVAIL 44
23. define AST_CAUSE_PRE_EMPTED 45
24. define AST_CAUSE_FACILITY_NOT_SUBSCRIBED 50
25. define AST_CAUSE_OUTGOING_CALL_BARRED 52
26. define AST_CAUSE_INCOMING_CALL_BARRED 54
27. define AST_CAUSE_BEARERCAPABILITY_NOTAUTH 57
28. define AST_CAUSE_BEARERCAPABILITY_NOTAVAIL 58
29. define AST_CAUSE_BEARERCAPABILITY_NOTIMPL 65
30. define AST_CAUSE_CHAN_NOT_IMPLEMENTED 66
31. define AST_CAUSE_FACILITY_NOT_IMPLEMENTED 69
32. define AST_CAUSE_INVALID_CALL_REFERENCE 81
33. define AST_CAUSE_INCOMPATIBLE_DESTINATION 88
34. define AST_CAUSE_INVALID_MSG_UNSPECIFIED 95
35. define AST_CAUSE_MANDATORY_IE_MISSING 96
36. define AST_CAUSE_MESSAGE_TYPE_NONEXIST 97
37. define AST_CAUSE_WRONG_MESSAGE 98
38. define AST_CAUSE_IE_NONEXIST 99
39. define AST_CAUSE_INVALID_IE_CONTENTS 100
40. define AST_CAUSE_WRONG_CALL_STATE 101
41. define AST_CAUSE_RECOVERY_ON_TIMER_EXPIRE 102
42. define AST_CAUSE_MANDATORY_IE_LENGTH_ERROR 103
43. define AST_CAUSE_PROTOCOL_ERROR 111
44. define AST_CAUSE_INTERWORKING 127

/* Special Asterisk aliases */

1. define AST_CAUSE_BUSY AST_CAUSE_USER_BUSY
2. define AST_CAUSE_FAILURE AST_CAUSE_NETWORK_OUT_OF_ORDER
3. define AST_CAUSE_NORMAL AST_CAUSE_NORMAL_CLEARING
4. define AST_CAUSE_NOANSWER AST_CAUSE_NO_ANSWER
5. define AST_CAUSE_CONGESTION AST_CAUSE_NORMAL_CIRCUIT_CONGESTION
6. define AST_CAUSE_NOTDEFINED 0

Recommended SIP <-> ISDN Cause codes (from RFC3398)

Note: Asterisk 1.8 will allow to read SIP response codes in the dialplan via

${HASH(SIP_CAUSE,<channel-name>)}

So slave SIP channels now set HASH(SIP_CAUSE,<slave-channel-name>) on each response. This permits the master channel to know how each channel dialed in a multi-channel setup resolved in an individual way.

Asterisk 1.8 also comes with a ‘use_q850_reason’ configuration option for generating and parsing, if available:

Reason: Q.850;cause=<cause code>

It is implemented in some gateways for better passing PRI/SS7 cause codes via SIP.
Tilghman: “The only reason we implemented the passing back of the raw SIP code in the dialplan is that the conversion to cause is lossy. That is, several SIP status codes all map back to a single ISUP cause code, and there are legitimate reasons for wanting to know which status code was received. What SHOULD happen is that if use_q850_reason is set, then the cause sent to the core should simply be the cause code in this new SIP header (“Reason: …”), which you should be able to read in ${HANGUPCAUSE}.”
The destination channel dies right after your Dial statement exits, but you can retrieve the info in the channel that’s still alive :
exten => _XXX,n,Dial(SIP/${EXTEN})
exten => _XXX,n,NoOp(SIP return code : ${HASH(SIP_CAUSE,${CDR(dstchannel)})})

ISUP Cause value SIP response

1 unallocated number 404 Not Found
2 no route to network 404 Not found
3 no route to destination 404 Not found
16 normal call clearing — (*)
17 user busy 486 Busy here
18 no user responding 408 Request Timeout
19 no answer from the user 480 Temporarily unavailable
20 subscriber absent 480 Temporarily unavailable
21 call rejected 403 Forbidden (+)
22 number changed (w/o diagnostic) 410 Gone
22 number changed (w/ diagnostic) 301 Moved Permanently
23 redirection to new destination 410 Gone
26 non-selected user clearing 404 Not Found (=)
27 destination out of order 502 Bad Gateway
28 address incomplete 484 Address incomplete
29 facility rejected 501 Not implemented
31 normal unspecified 480 Temporarily unavailable

 
Response received Cause value in the REL

400 Bad Request 41 Temporary Failure
401 Unauthorized 21 Call rejected (*)
402 Payment required 21 Call rejected
403 Forbidden 21 Call rejected
404 Not found 1 Unallocated number
405 Method not allowed 63 Service or option unavailable
406 Not acceptable 79 Service/option not implemented (+)
407 Proxy authentication required 21 Call rejected (*)
408 Request timeout 102 Recovery on timer expiry
410 Gone 22 Number changed (w/o diagnostic)
413 Request Entity too long 127 Interworking (+)
414 Request-URI too long 127 Interworking (+)
415 Unsupported media type 79 Service/option not implemented (+)
416 Unsupported URI Scheme 127 Interworking (+)
420 Bad extension 127 Interworking (+)
421 Extension Required 127 Interworking (+)
423 Interval Too Brief 127 Interworking (+)
480 Temporarily unavailable 18 No user responding
481 Call/Transaction Does not Exist 41 Temporary Failure
482 Loop Detected 25 Exchange – routing error
483 Too many hops 25 Exchange – routing error
484 Address incomplete 28 Invalid Number Format (+)
485 Ambiguous 1 Unallocated number
486 Busy here 17 User busy
487 Request Terminated — (no mapping)
488 Not Acceptable here — by Warning header
500 Server internal error 41 Temporary failure
501 Not implemented 79 Not implemented, unspecified
502 Bad gateway 38 Network out of order
503 Service unavailable 41 Temporary failure
504 Server time-out 102 Recovery on timer expiry
504 Version Not Supported 127 Interworking (+)
513 Message Too Large 127 Interworking (+)
600 Busy everywhere 17 User busy
603 Decline 21 Call rejected
604 Does not exist anywhere 1 Unallocated number
606 Not acceptable — by Warning header

(*) In some cases, it may be possible for a SIP gateway to provide
credentials to the SIP UAS that is rejecting an INVITE due to
authorization failure. If the gateway can authenticate itself, then
obviously it SHOULD do so and proceed with the call; only if the
gateway cannot authenticate itself should cause code 21 be sent.

(+) If at all possible, a SIP gateway SHOULD respond to these
protocol errors by remedying unacceptable behavior and attempting to
re-originate the session. Only if this proves impossible should the
SIP gateway fail the ISUP half of the call.

When the Warning header is present in a SIP 606 or 488 message, there
may be specific ISDN cause code mappings appropriate to the Warning
code. This document recommends that ’31 Normal, unspecified’ SHOULD
by default be used for most currently assigned Warning codes. If the
Warning code speaks to an unavailable bearer capability, cause code
’65 Bearer Capability Not Implemented’ is a RECOMMENDED mapping.

Cisco Loopback Tests

Loopback Modes

There are three main loopback modes as follows: local, network (both line and payload), and remote (line and payload). Specify the loopback format using the loopback [ local | network | remote ] command.

Examples of specific loopback modes follow:

• Set the first T1 into local loopback as follows:

   Router#   config t  
  Enter configuration commands, one per line. End with CNTL/Z.
  Router(config)#   interface serial 3/0:1  
  Router(config-if)#   loopback local   

  In the preceding example, local loopback loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network.

• Set the first T1 into network line loopback as follows:

   Router#   config t  
  Enter configuration commands, one per line. End with CNTL/Z.
  Router(config)#   interface serial 3/0:1  
  Router(config-if)#   loopback network line   

  In the preceding example, network line loopback loops the data back toward the network (before the T1 framer).

• Set the first T1 into network payload loopback as follows:

   Router#   config t  
  Enter configuration commands, one per line. End with CNTL/Z.
  Router(config)#   interface serial 3/0:1  
  Router(config-if)#   loopback network payload   

  In the preceding example, network payload loopback loops just the payload data back toward the network at the T1 framer.

• The syntax of the loopback remote command follows:

     loopback   [  remote   {  line   {  fdl ansi   |   inband  } |   payload fdl ansi  }] 

  Set the first T1 into remote line inband loopback, as follows:

   Router#   config t  
  Enter configuration commands, one per line.  End with CNTL/Z.
  Router(config)#   int serial 3/0:1  
  Router(config-if)#   loop remote line inband   

  In the preceding example, remote line inband loopback sends a repeating 5-bit inband pattern (of 00001) to the remote end requesting that it enter into a network line loopback.

  Set the first T1 into remote line FDL ANSI bit loopback, as follows:

   Router#   config t  
  Enter configuration commands, one per line.  End with CNTL/Z.
  Router(config)#   int serial 3/0:1  
  Router(config-if)#   loop remote line fdl ansi   

  In the preceding example, remote line FDL ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 00001110 11111111) to the remote end requesting that it enter into a network line loopback.

  Set the first T1 into remote payload FDL ANSI bit loopback, as follows:

   Router#   config t  
  Enter configuration commands, one per line.  End with CNTL/Z.
  Router(config)#   int serial 3/0:1  
  Router(config-if)#   loop remote payload fdl ansi   

  In the preceding example, remote payload ANSI bit loopback sends a repeating 16-bit ESF data link code word (of 00010100 11111111) to the remote end requesting that it enter into a network payload loopback.

Checking Bit Errors Using a BERT

To check bit errors using a bit error test (BERT), use the following command:

 [  no  ]   t1     t1 channel     bert pattern   {  2^15   |   2^20   |   2^23   |   0s   | 
  1s  }   interval     minutes    

where t1 channel is 1-28, 2^15 is an exponential number that represents a pseudo-random repeating pattern that is 32767 bits long, 2^20 is a pseudo-random repeating pattern that is 1048575 bits long, 2^23 is a pseudo-random repeating pattern that is 8388607 bits long, 0s is a pattern of all zeroes (00000000…), 1s is a pattern of all 1s (111111…), and minutes are 1-14400, which designate the time the BERT will run. To stop the BERT, use the optional no form of the command. Following is an example of this command, where the pseudo-random pattern 2^20 is sent and repeats on the first T1 channel for 60 minutes:

 Router#   t1 1 bert pattern 2^20 interval 60   

Note that the BERT command is not saved in NVRAM. The test patterns from the PA-CT3/4T1 port adapter are framed test patterns; therefore, they are inserted into the payload of a framed T1 signal.

To display the BERT results, use the following EXEC commands: sh cont t3 number or sh cont t3 number brief . Following are examples of displaying BERT results output:

1. Display BERT output results during a test, as follows:

    Router#   sh cont t3 5/0 b  
   T3 5/0 is up.
   CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 20.2.0
     Mx H/W version : 2, Mx ucode ver : 1.25
     Applique type is Channelized T3
     No alarms detected.
     FEAC code received : No code is being received
     Framing is M23, Line Code is B3ZS, Clock Source is Internal.
     T1 1 is down, speed: 1536 kbs, non-inverted data
     timeslots: 1-24
     FDL per ANSI T1.403 and AT&T 54016 spec.
     Configured for FDL Remotely Line Looped
     No alarms detected.
     Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
     BERT test result (running)
         Test Pattern : All 0's, Status : Sync, Sync Detected : 1
         Interval : 4 minute(s), Time Remain : 4 minute(s)
         Bit Errors(Sync BERT Started) : 0 bits
         Bit Errors(Sync last Sync) : 0 bits , Bits Received : 7 Mbits 

   Note When the T1 is under BERT, its line state is down. When under BERT (in the running state), the “Total Bit Errors” value is not valid if the “Status” field is “Not Sync.”

2. When the test is done, display BERT results output as follows:

    Router#   sh cont t3 5/0 b  
   T3 5/0 is up.
     CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 20.2.0
     Mx H/W version : 2, Mx ucode ver : 1.25
     Applique type is Channelized T3
     No alarms detected.
     FEAC code received : No code is being received
     Framing is M23, Line Code is B3ZS, Clock Source is Internal.
     T1 1 is up, speed: 1536 kbs, non-inverted data
     timeslots: 1-24
     FDL per ANSI T1.403 and AT&T 54016 spec.
     Configured for FDL Remotely Line Looped
     No alarms detected.
     Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
     BERT test result (done)
         Test Pattern : All 0's, Status : Not Sync, Sync Detected : 1
         Interval : 4 minute(s), Time Remain : 0 minute(s)
         Bit Errors(Sync BERT Started) : 0 bits
         Bit Errors(Sync last Sync) : 0 bits , Bits Received : 368 Mbits 

   Note The “Status” field is irrelevant when the BERT is done. If the “Sync Detected” counter is 0, the Bit Errors fields have no meaning.

3. When the test is stopped prematurely, display BERT results output as follows:

    Router#   sh cont t3 5/0 b  
   T3 5/0 is up.
     CT3 H/W Version : 4, CT3 ROM Version : 0.116, CT3 F/W Version : 20.2.0
     Mx H/W version : 2, Mx ucode ver : 1.25
     Applique type is Channelized T3
     No alarms detected.
     FEAC code received : No code is being received
     Framing is M23, Line Code is B3ZS, Clock Source is Internal.
     T1 1 is up, speed: 1536 kbs, non-inverted data
     timeslots: 1-24
     FDL per ANSI T1.403 and AT&T 54016 spec.
     Configured for FDL Remotely Line Looped
     No alarms detected.
     Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
     BERT test result (done)
         Test Pattern : All 0's, Status : Not Sync, Sync Detected : 1
         Interval : 4 minute(s), Time Remain : 2 minute(s) (unable to complete)
         Bit Errors(Sync BERT Started) : 0 bits
         Bit Errors(Sync last Sync) : 0 bits , Bits Received : 368 Mbits 

   Note In the preceding three examples, the “Sync Detected” counter indicates the number of times the pattern sync is detected (from No Sync to Sync), the “Bit Errors(Sync BERT Started)” counter indicates the number of bit errors during BERT, and the “Bit Errors(Sync last Sync)” counter shows the number of bit errors since the last pattern sync is detected.

ISDN Cause Codes

ISDN Cause Codes

Cause No. 0
This is usually given by the router when none of the other codes apply. This cause usually occurs in the same type of situations as cause 1, cause 88, and cause 100.

Cause No. l – Unallocated (unassigned) number.
This cause indicates that the destination requested by the calling user cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

What it usually means:

1. The SPIDS may be incorrectly entered in the router or the Telco switch, giving a SPID failure in the router logs.
2. The ISDN phone number being dialed by the router is invalid and the telco switch cannot locate the number to complete the call, as it is invalid.
3. On long distance calls, the call cannot be properly routed to its destination.

Cause No. 2 – No route to specified transit network (national use).
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 not serve the equipment which is sending this cause.

Cause No. 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 No. 4 – send special information tone.
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).
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.
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.
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.
This cause indicates the call is being preempted.

Cause No. 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 No. 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.

What it means:
This could be almost anything; it is the vaguest of the cause codes. The call comes down normally, but the reasons for it could be:

1. Bad username or password
2. Router’s settings do not match what is expected by the remote end.
3. Telephone line problems.
4. Hung session on remote end.

Cause No. 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.

What is means:
Calling end is busy.
Cause No. 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 time allocated.

What it means:
The equipment on the other end does not answer the call. Usually this is a misconfiguration on the equipment being called.
Cause No. 19 – no answer from user (user alerted).
This cause is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time. Note – This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.

Cause No. 20 – subscriber absent.
This cause value is used when a mobile station has logged off. Radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface.

Cause No. 21 – call rejected.
This cause indicates that the equipment sending this cause does not wish to accept this call. although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. This cause may also be generated by the network, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection.

What it means:
This is usually a telco issue. The call never reaches the final destination, which can be caused by a bad switch translation, or a misconfiguration on the equipment being called.
Cause No. 22 – number changed.
This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this cause, cause no. 1, unallocated (unassigned) number shall be used.

Cause No. 26 – non-selected user clearing.
This cause indicates that the user has not been awarded the incoming call.

Cause No. 27 – destination out of order.
This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signal message was unable to be delivered to the remote party; e.g., a physical layer or data link layer failure at the remote party or user equipment off-line.

Cause No. 28 – invalid number format (address incomplete).
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.

Cause No. 29 – facilities rejected.
This cause is returned when a supplementary service requested by the user cannot be provide by the network.

Cause No. 30 – response to STATUS INQUIRY.
This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY.

Cause No. 31 – normal. unspecified.
This cause is used to report a normal event only when no other cause in the normal class applies.

Cause No. 34 – no circuit/channel available.
This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

What it means:
There is no place on the Public Telephone network to place the call; the call never gets to its destiation. This is usually a temporary problem.
Cause No. 35 – Call Queued.

Cause No. 38 – network out of order.
This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time e.g., immediately re-attempting the call is not likely to be successful.

Cause No. 39 – permanent frame mode connection out-of-service.
This cause is included in a STATUS message to indicate that a permanently established frame mode connection is out-of-service (e.g. due to equipment or section failure)

Cause No. 40 – permanent frame mode connection operational.
This cause is included in a STATUS message to indicate that a permanently established frame mode connection is operational and capable of carrying user information.

Cause No. 41 – temporary failure.

This cause indicates that the network is not functioning correctly and that the condition is no likely to last a long period of time; e.g., the user may wish to try another call attempt almost immediately.

What it means:
This means that there is a temporary failure at the physical layer on the ISDN network. If you remove the ISDN cable from the Netopia, you would see this. It’s usually temporary.
Cause No. 42 – switching equipment congestion.
This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

What it means:
Just too much going on at this point on the ISDN network to get the call through to its destination.
Cause No. 43 – access information discarded.
This cause indicates that the network could not deliver access information to the remote user as requested. i.e., user-to-user information, low layer compatibility, high layer compatibility or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.

Cause No. 44 – requested circuit/channel not available.
This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

Cause No. 46 – precedence call blocked.
This cause indicates that there are no predictable circuits or that the called user is busy with a call of equal or higher preventable level.

Cause No. 47 – resource unavailable, unspecified.
This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

Cause No. 49 – Quality of Service not available.
This cause is used to report that the requested Quality of Service, as defined in Recommendation X.213. cannot be provided (e.g., throughput of transit delay cannot be supported).

Cause No. 50 – requested facility not subscribed.
This cause indicates that the user has requested a supplementary service which is implemented by the equipment which generated this cause but the user is not authorized to use.

What it means:
The switch looks at the number being dialed and thinks it is for another service rather than ISDN. If the phone number is put in the correct format, the call should be placed properly. There are no standards for this, all Telcos have their own system for programming the number formats that the switches will recognize. Some systems want to see 7 digits, some 10, and others 11.
Cause No. 52 – outgoing calls barred.

Cause No. 53 – outgoing calls barred within CUG.
This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call. Outgoing calls are not allowed for this member of the CUG.

Cause No. 54 – incoming calls barred

Cause No. 55 – incoming calls barred within CUG.
This cause indicates that although the calling party is a member of the CUG for the incoming CUG call. Incoming calls are not allowed for this member of the CUG.

Cause No. 57 – bearer capability not authorized.
This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but the user is not authorized to use.

Cause No. 58 – bearer capability not presently available.
This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

Cause No. 62 – inconsistency in outgoing information element.
This cause indicates an inconsistency in the designated outgoing access information and subscriber class.

Cause No. 63 – service or option not available. unspecified.
This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.

Cause No. 65 – bearer capability not implemented.
This cause indicates that the equipment sending this cause does not support the bearer capability requested.

What it means:

1. In most cases, the number being called is not an ISDN number but an analog destination.
2. The equipment is dialing at a faster rate than the circuitry allows, for example, dialing at 64K when only 56K is supported.

Cause No. 66 – channel type not implemented.
This cause indicates that the equipment sending this cause does not support the channel type requested.

Cause No. 69 – requested facility not implemented.
This cause indicates that the equipment sending this cause does not support the requested supplementary services.

Cause No. 70 – only restricted digital information bearer capability is available.
This cause indicates that the calling party has requested an unrestricted bearer service but the equipment sending this cause only supports the restricted version of the requested bearer capability.

Cause No. 79 – service or option not implemented unspecified.
This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

Cause No. 81 – invalid call reference value.
This cause indicates that the equipment sending this cause has received a message with a call reference which is not currently in use on the user-network interface.

Cause No. 82 – identified channel does not exist.
This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the interface for a call. For example, if a user has subscribed to those channels on a primary rate interface numbered from l to 12 and the user equipment or the network attempts to use channels 3 through 23, this cause is generated.

Cause No. 83 – a suspended call exists, but this call identify does not. This cause indicates that a call resume has been attempted with a call identity which differs from that in use for any presently suspended call(s).

Cause No. 84 – call identity in use.
This cause indicates that the network has received a call suspended request containing a call identity (including the null call identity) which is already in use for a suspended call within the domain of interfaces over which the call might be resumed.

Cause No. 85 – no call suspended.
This cause indicates that the network has received a call resume request containing a call identity information element which presently does not indicate any suspended call within the domain of interfaces over which calls may be resumed.

Cause No. 86 – call having the requested call identity has been cleared.
This cause indicates that the network has received a call resume request containing a call identity information element indicating a suspended call that has in the meantime been cleared while suspended (either by network time-out or by the remote user).

Cause No. 87 – user not a member of CUG.
This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG or that the calling user is an ordinary subscriber calling a CUG subscriber.

Cause No. 88 – incompatible destination.
This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility. high layer compatibility or other compatibility attributes (e.g., data rate) which cannot be accommodated.

What it means:

1. This usually means that the Number To Dial in the Connection Profile is in the wrong format. You may need to dial a 10 or 11 digit number, or dial a 9 in front of the number if it is a Centrex line.
2. This problem may also give a Cause 111.
3. Dialing at the wrong line speed can also give this Cause.

Cause No. 90 – non-existent CUG.
This cause indicates that the specified CUG does not exist.

Cause No. 91 – invalid transit network selection (national use).
This cause indicates that a transit network identification was received which is of an incorrect format as defined in Annex C/Q.931

Cause No. 95 – invalid message, unspecified.
This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Cause No. 96 – mandatory information element is missing.
This cause indicates that the equipment sending this cause has received a message which is missing an information element which must be present in the message before that message can be processed.

What it means:
This is rarely seen in North America but usually means that the number that is being dialed is in the wrong format, (similar to cause 88). Some part of the format being used is not understood by either the remote side equipment or the switching equipment between the source and destination of the call.
Cause No. 97 – message type non-existent or not implemented.
This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined of defined but not implemented by the equipment sending this cause.

Cause No. 98 – message not compatible with call state or message type non-existent.
This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state.

Cause No. 99 – Information element / parameter non-existent or not implemented.
This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause No. 100 – Invalid information element contents.
This cause indicates that the equipment sending this cause has received and information element which it has implemented; however, one or more of the fields in the information element are coded in such a way which has not been implemented by the equipment sending this cause.

What it means:
Like cause 1 and cause 88, this usually indicates that the ISDN number being dialed is in a format that is not understood by the equipment processing the call. SPIDs will sometimes fail to initialize with a Cause 100, or a call will fail with this cause.
Cause No. 101 – message not compatible with call state.
This cause indicates that a message has been received which is incompatible with the call state.

Cause No. 102 – recovery on timer expiry.
This cause indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures.

What it means:
This is seen in situations where ACO (Alternate Call Offering) is being used. With this type of call pre-emption, the Telco switch operates a timer. For example, when an analog call is placed to a Netopia router that has two B Data Channels in place, the router relinquishes the second channel, but if it doesn’t happen in the time allotted by the switch programming, the call will not ring through and will be discarded by the switch.
Cause No. 103 – parameter non-existent or not implemented – passed on (national use).
This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged.

Cause No. 110 – message with unrecognized parameter discarded.
This cause indicates that the equipment sending this cause has discarded a received message which includes a parameter that is not recognized.

Cause No. 111 – protocol error, unspecified.
This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

Cause No. 127 – Intel-working, unspecified.
This cause indicates that an interworking call (usually a call to 5W56 service) has ended.

Notes about Cause Codes over 128
Cause code values of 128 and higher aren’t sent over the network. A terminal displaying a value 128 or higher and claiming it is a cause code arguably has a bug or is implementing some proprietary diagnostic code (not necessarily bad). Some commendation has cause codes listed with numbers higher than 128, but at this time they are proprietary in nature.

The PRI equipment vendors are the most likely to use these codes as they have been using proprietary messages in the facilities data link for some time now (there is an as yet undefined area in the FDL which is big enough to carry small datagrams or messages). It is typically used to pass proprietary control or maintenance messages between multiplexers.

Provisioning para ATAs LinkSys PAP2

Usando um tftp free, e também tem como utilizar um server web porém irei falar utilizando um tftp local

Instale um tftp server, por exemplo: SolarWinds TFTP, para testar por enquanto desabilite seu firewall ou abra a porta UDP 69.

a seguir crie um arquivo ata_conf.txt, salve este arquivo dentro do seu tftp server.

Configurando o arquivo de texto para que seu ATA pegue as configurações.

   <flat-profile>
	<Resync_Periodic>600</Resync_Periodic>
	
<!-- tag case appears to be important -->
<!-- configurações de usuário e senha do ata -->
 	<Admin_Passwd></Admin_Passwd>
 	<User_Passwd></User_Passwd>

<!-- system, optional network configuration -->
 	<HostName>spa</HostName>
 	<Domain>dominio.com.br</Domain>
 	<Primary_DNS>servidordns1</Primary_DNS>
 	<Secondary_DNS>servidordns2</Secondary_DNS>
 	<DNS_Server_Order>DHCP,Manual</DNS_Server_Order>
 	<Primary_NTP_Server>ntp.exemplo.com.br</Primary_NTP_Server>

<!-- line 1, proxy and registration -->
 	<Proxy_1_>voip.exemplo.com.br</Proxy_1_>

<!-- line 1, subscriber information -->
 	<Display_Name_1_>1001</Display_Name_1_>
 	<User_ID_1_>1001</User_ID_1_>
 	<Password_1_>supersenha</Password_1_>
	<Dial_Plan_1_>(000xxxxx.|0xxxxxxxx|0xxxxxxxxxxS0|00800xxxx.|1xxxS0|*8S0|*xx|xxx)</Dial_Plan_1_>

<!-- line 2, proxy and registration -->
 	<Proxy_2_>voip.exemplo.com.br</Proxy_2_>

<!-- line 2, subscriber information -->
 	<Display_Name_2_>1002</Display_Name_2_>
 	<User_ID_2_>1002</User_ID_2_>
 	<Password_2_>supersenha</Password_2_>
	<Dial_Plan_2_>(000xxxxx.|0xxxxxxxx|0xxxxxxxxxxS0|00800xxxx.|1xxxS0|*8S0|*xx|xxx)</Dial_Plan_2_>

	<Call_Return_Code></Call_Return_Code>
	<Blind_Transfer_Code></Blind_Transfer_Code>
	<Call_Back_Act_Code></Call_Back_Act_Code>
	<Call_Back_Deact_Code></Call_Back_Deact_Code>
	<Cfwd_All_Act_Code></Cfwd_All_Act_Code>
	<Cfwd_All_Deact_Code></Cfwd_All_Deact_Code>
	<Cfwd_Busy_Act_Code></Cfwd_Busy_Act_Code>
	<Cfwd_Busy_Deact_Code></Cfwd_Busy_Deact_Code>
	<Cfwd_No_Ans_Act_Code></Cfwd_No_Ans_Act_Code>
	<Cfwd_No_Ans_Deact_Code></Cfwd_No_Ans_Deact_Code>
	<Cfwd_Last_Act_Code></Cfwd_Last_Act_Code>
	<Cfwd_Last_Deact_Code></Cfwd_Last_Deact_Code>
	<Block_Last_Act_Code></Block_Last_Act_Code>
	<Block_Last_Deact_Code></Block_Last_Deact_Code>
	<Accept_Last_Act_Code></Accept_Last_Act_Code>
	<Accept_Last_Deact_Code></Accept_Last_Deact_Code>
	<CW_Act_Code></CW_Act_Code>
	<CW_Deact_Code></CW_Deact_Code>
	<CW_Per_Call_Act_Code></CW_Per_Call_Act_Code>
	<CW_Per_Call_Deact_Code></CW_Per_Call_Deact_Code>
	<Block_CID_Act_Code></Block_CID_Act_Code>
	<Block_CID_Deact_Code></Block_CID_Deact_Code>
	<Block_CID_Per_Call_Act_Code></Block_CID_Per_Call_Act_Code>
	<Block_CID_Per_Call_Deact_Code></Block_CID_Per_Call_Deact_Code>
	<Block_ANC_Act_Code></Block_ANC_Act_Code>
	<Block_ANC_Deact_Code></Block_ANC_Deact_Code>
	<DND_Act_Code></DND_Act_Code>
	<DND_Deact_Code></DND_Deact_Code>
	<CID_Act_Code></CID_Act_Code>
	<CID_Deact_Code></CID_Deact_Code>
	<CWCID_Act_Code></CWCID_Act_Code>
	<CWCID_Deact_Code></CWCID_Deact_Code>
	<Dist_Ring_Act_Code></Dist_Ring_Act_Code>
	<Dist_Ring_Deact_Code></Dist_Ring_Deact_Code>
	<Vertical_Service_Announcement_Codes></Vertical_Service_Announcement_Codes>
	<Time_Zone>GMT-03:00</Time_Zone>

</flat-profile>