Avaya Site Administration 1

[ITSurvivor]

Greetings all,

I am inheriting an Avaya Definity G3i, I believe, and the ASA has been working for quite a while. This past Friday, from the ASA machine trying to connect to the PBX throws up "Communications error: network connection failed. We can ping the ip address from the ASA box to the PBX server and the PBX is running. Any advice on why we all of a sudden can't connect to the PBX server from the ASA box?

Much appreciated all,

Richard

 

[smokinjoe2938]

have you checked your settings in asa? system/properties/connection?

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[ITSurvivor]

Good morning smokingjoe,

Thank you for the response.

On the system/properties/connection configuration we have Default Connection Id: 1 Type - Network Dial/Host - 10.1.2.45 Port - 5111 Serial Device - blank.

We tried different port number and even swapped the network cable to a different port on the switch.

Any other advice, smokingjoe?

Richard

 

[smokinjoe2938]

try port 5023 and retest

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[AvayaTier3]

Port is determined by translations for the clan SAT services

change ip-services                                              Page   1 of   1

                                   IP SERVICES
 Service     Enabled     Local        Local       Remote      Remote
  Type                   Node         Port        Node        Port
SAT           y      CLAN             5111    admin           0

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[smokinjoe2938]

As he can not access the pbx and it currently does not work it was worth a try, I understand what you are saying but who knows if someone made a change recently.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[mattKnight]

This isn't something reaaly stupid like a duplicate IP address?

(unplug the network lead from the PABX and see if the ping drops)

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[ITSurvivor]

Hello smokinjoe and AvayaTier3,

I do thank you both for your time and reply. Smokinjoe, changing to port 5023 WORKED! I do thank you so much for that tip and resolution and also AvayaTier3 for the command. That will be very helpful in the future.

This forum and you gentlemen, ROCKS!

Richard

 

[ITSurvivor]

Hi Matt,

No, LOL, nothing stupid like that happened. But it was the port change that smokinjoe suggested that resolved the issue. We have tried other ports that didn't work but perhaps not that port.

Thank you all that took the time to assist this newbie.

Richard

 

[AvayaTier3]

For legacy g3si and g3csi with clans:
The only ports that will work are defined for each clan on the ip-services form.

For Linux base servers, port 22 and 5022 use ssh for the server IP address.
port 23 and 5023 use telnet for the server IP address.
22 and 23 will work for Linux access to each server.
5022 and 5023 will only work for direct SAT on the active server.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]