Skip to main content

AVAYA TRUNK CHECKING WITH VODAFONE PRI


check status of AVAYA TRUNK CHECKING WITH VODAFONE PRI

Today, I am going to show you how to check the PRI status in AVAYA CALL MANAGER (CM)

first up all we have to check the group no. of the PRI using the command list trunk-group.

in the above snaps we can see that the trunk group is 35.

now we can check the status of the PRI using the status trunk 35.


we can see in the snapshot out-of-service means the PRI is down, or having some connectivity issue on the PRI.


we have to make sure that if we are using the VODAFONE PRI then the options Disable Restarts in the DS1 CIRCUIT RACK must be enable means "y" should be there.
As per as the ISP (VODAFONE) suggestion it must be enabled.


otherwise we may face some issue.

To change the setting of the DS1 first we have to check the port no which is shown in the above images, and also marked in the below images:



now we can check the DS1 CIRCUIT RACK status like this:


you can see that the Disable Restarts is on the "n" state we have to make it "y"

before proceeding we have to busyout the ds1 board, if the board is not being busyout then it will show the warning like this:


The ds1 board is being busyout like this:


after that we can change the ds1 broad like this :


Now we can release the ds1 and check the PRI status.

after changing the Disable Restarts is on the "y" we can check the PRI status.




and for more information about the PRI we can follow the below information for our reference:

DS1 ISDN Trunk Service States

The status trunk command displays the following possible service states for ISDN trunks. Table 213 gives recommended procedures for each state.
  • In-Service (INS)
The B-channel is in its normal operating state.
  • Out-of-Service/Far-End (OOS/FE)
A B-Channel is initialized to this state when administered. The switch sends messages to the far-end to negotiate the B-channel into service. If the far-end does not respond to the messages within a certain time period, then the service state remains out-of-service and maintenance will periodically resend the messages. The trunk is unusable for incoming and outgoing calls.
  • Out-of-Service/Near-End (OOS/NE)
This is the state of the trunk when the NPE Crosstalk Test fails or when the trunk is busied out by system technician. In this state, the trunk is unusable for incoming or outgoing calls. No messages are sent to the far-end until the signaling link comes back into service or the trunk is released by system technician.
  • Maintenance/Far-End (MTC/FE)
This state is reached when the far-end does not respond to messages sent over the signaling link for a particular trunk after a certain amount of time. This state is different from OOS/FE since the signaling link must have initially been up and the B-Channels in-service. The switch will periodically send messages to the far-end to try to negotiate the trunk (B-channel) into service. The trunk is unusable for outgoing calls but will service incoming call requests from the far-end. Note that transitions into MTC/FE do not drop stable calls. Therefore, if the service state changes from in-service to MTC/FE, then stable calls are unaffected.
  • Maintenance/Near-End (MTC/NE)
The trunk (B-channel) is in this state if the signaling channel (ISDN-LNK) is busied out by system technician. The trunk (B-channel) is also temporarily in this state if system technician has issued a test trunk trunk group/trunk member long command. This command will execute the ISDN-PRI test call. This test will change the state of the trunk member to MTC/NE for the duration of the test unless a call request comes in from the far-end. In that case, the test would abort. Note that transitions into MTC/NE do not drop stable calls. In this state, the B-Channel is not usable for new incoming or outgoing calls.
  • Pending States
In addition to one of the above components, the service state may have a pending component, indicating that the switch is waiting for a reply from the far-end. These service states remain in effect until either a response is received or the allotted waiting time expires.
    • Pending-in-Service
The near-end is waiting for a response from the far-end to a B-channel maintenance message requesting that the B-channel be transitioned to in-service.
    • Pending-Maintenance
This state is supported only by systems using country protocol 1 (including US). The near-end is waiting for a response from the far-end to a maintenance message requesting that the B-channel be transitioned to the maintenance service state.
  • Call Activity States
The in-service service state also has a call activity component.
    • Active
A call is connected over the B-channel (for example, in-service/active).
    • Idle
There is no call currently on the B-channel (for example, in-service/idle).
Table 213. Service States �
Service State
Alarm*
Possible Cause
Possible Solution
out-of-service/NE 
Warning
Trunk is demand busied out.
Enter release trunk grp#/mbr#.
None
DS1 or MM-DS1 media module lost its signal.
Is the media module or cable removed? Is the far-end switch restarting? Check media module using procedures in DS1-MM.
out-of-service/FE 
Warning
Unadministered far-end
Administer corresponding trunk on far-end switch.
Warning
The far-end trunk is busied out.
Check the status of the far-end switch.
pending-in-service, pending-maint 
None
Maintenance message was sent and the switch is waiting up to 2 min. for a reply from the far-end.
Wait 2 minutes and check service state after the pending state has cleared.
maint-NE 
None
ISDN test call in progress (test trunk long and test isdn-testcall commands)
Wait several minutes for test to finish and check status again.
None
System link has been busied out by command.
Check link status. Release link with release link link#.
maint-FE 
Warning
Signaling channel has been down for over 90 sec.
Consult ISDN-SGRP and/or ISDN-LNK. Far-end signaling channel may be busied out, or the far-end switch may currently be restarting.
Warning
Repeated failure of far end to respond to messages.
Maintenance software will periodically try to resend messages. You can speed the process withtest trunk grp#/mbr# and/or test signaling-gr #.
Warning
The far-end trunk is being tested.
Check status of the far-end switch. Wait for testing to finish.
in-service 
None
Normal operating state
*ISDN-TRK alarms; alarms against other objects may also be present.










Thanks for reading.

Happy learning...



Comments

Popular posts from this blog

ArubaOS-CX, ArubaOS- Switch, Comware and Cisco IOS

The command line comparison demonstrated for 4 different OS of the switches, I think this will help you to understand the configuration level deployment. Comware Differences If you are familiar with either the ArubaOS-Switch CLI or the Cisco IOS CLI, you will notice that the  Comware CLI is organized slightly differently . Comware was designed for Internet service providers (ISPs). Many features and functions—such as security and Quality of Service (QoS)—are multi-tiered to  support the different needs of multiple entities accessing the same switch. ArubaOS-CX ArubaOS switch (now the Aruba OS), HPE Comware version 7 Cisco IOS ArubaOS-CX operating system runs on the 8400 and 8320 switches. ArubaOS Switch operating system runs on Aruba 2530 , Aruba 2920 , Aruba 2930F , Aruba 2930M , Aruba 3810M , Aruba 5400R , HPE 2620 , HPE 3500 , HPE 5400 and HPE 3800 switch platforms. HPE Comware7 operating system runs on HPE FF 12900 , HPE 12500 , HPE 5120/5...

HP A5120 Configuration

Today I am going to configure the HP A5120-24G EI Switch. We require the COM1 Port on the system and console cable. The pictures are shown below: COM1: Console Cable: Or You can use converter like this to connect to your laptop USB port : Connect the cable to the console cable with your system and power on the switch and hit Enter Press ENTER to get started,  you will able to see like this: <HPSWITCH> #Apr 26 12:19:44:864 2000 HPSWITCH SHELL/4/LOGIN:  Trap 1.3.6.1.4.1.25506.2.2.1.1.3.0.1: login from Console %Apr 26 12:19:44:995 2000 HPSWITCH SHELL/5/SHELL_LOGIN: Console logged in from aux0. <HPSWITCH> <HPSWITCH> As we know that the cisco having three stage to get into the switch console, just like same here. user mode : > privilege mode : # and the global config mode: config# same structures are here but little more differ from the Cisco here we have the user mo...