IP phone accross Lan to Lan VPN 2

[mhypolite]

Hello, i have an Avaya Difinity system with Medpro board, have 4620 IP sets, they work fine in the main site where the PBX is, there is a remote office with a LAN to LAN VPN in place, when i carry the ip phone to the remote office and reconfigure the ip address manually, and reassign the extension and password, i get the folling error after it restarts:

2011 registration
no signaling connection

there are no firewall restrictions over the VPN.

Any help is greatly appreciated. Thanks

 

[Toni269]

We installed ours at another site and I had the entire process documented, you may want to check this to see if maybe a step was missed? (Substitue xxx.xxx.xx.xx for IP addresses)

Following are the network / system changes necessary to support the Avaya IP phones:

A) Configuration Files
B) Installation of TFTP server
C) Modifications to DHCP Scopes
D) Modifications to Routing Interfaces
E) Modifications to VOIP Phones

These configuration changes are described in greater detail below:


Configuration Files

The Avaya IP phones upon startup will request access to two files that are to be located on the TFTP server that will be installed in the next step. These files are specific to our infrastructure and may need to be modified in order to operate outside of 3E Carlsbad. Below are the contents of these two configuration files:

46XXSETTINGS.TXT

#############################################################
## Avaya 46xx IP Telephone Settings Script
## File Created on: 12/22/2003
## See the LAN Administrators Guide for
## more details on using this file.


## Use "##" without quotes to comment out a line.
## To activate a setting below, set the parameter
## to the appropriate value for your network and
## remove the "## " from the begining of the line.

## To include whitespaces in a value,
## the entire value must be enclosed in double quotes.
## example:
## SET PARAM "value1 value2"

## To set different set types to different values, use
## the "IF" keyword statement.
## See the LAN Administrators Guide for more details.

## Some of the values listed below have default settings which
## are used by the IP Telephones even if they are commented out
## in this file. For a list of those settings and their default
## values, see the LAN Administrators Guide.

#############################################################

#############################################################
##### COMMON SETTINGS - Applies to all 4600 IP Telephones####

###### Domain Settings ######

## Your domain
## NOTE: It is recommended that DOMAIN be set via DHCP.
## If you set your DOMAIN via DHCP, do not set it here
## as it will over ride your DHCP setting.
## example:
SET DOMAIN 3ecompany.com

## Your Domain Name Server
## NOTE: It is recommended that Domain Name Server be set via DHCP.
## If you set your Domain Name Server via DHCP, do not set it here
## as it will over ride your DHCP setting.
## example:
SET DNSSRVR xxx.xxx.xx.xx

#############################################################
############# ==== END OF COMMON SETTINGS ==== ##############

###############################################################
###### Settings for the 4610, 4620 and 4630 IP Telephones #####

############## Enhanced Local Dialing Rules #################

## These settings effect certain dialing behaviors on the 4610,
## 4620 and 4630 phones. These include "Click to Dial" and
## "Add to Speed Dial" links shown on the web browser applications
## and incoming and missed call log entries. These settings also
## apply to dialable numbers reurned from searches on the 4630
## LDAP directory application.

## Telephone Country Code
## example: For United States it is '1'
SET PHNCC 1

## Telephone dial plan length (the length of an internal extension number).
## For example, if your extension is 12345, your dial plan
## length is 5.
## example:
SET PHNDPLENGTH 5

## Telephone international access code
## For the USA, the code is 011.
## example:
SET PHNIC 011

## Telephone long distance access code
## example:
SET PHNLD 1

## Length of national telephone number
## For example, 800-555-1111 is a length of 10.
## example:
SET PHNLDLENGTH 10

## Outside line access code
## The number you press to make an outside call.
## example:
SET PHNOL 9
#####################################################################

################# Application Access Settings #######################

## Use this setting to restrict access to certain 4610, 4620
## and 4630 applications.

## When APPSTAT is set to 0, Call Log and Redial are suppressed and,
## changes to Speed Dial are not allowed.

## when APPSTAT is set to 1, Call Log, Redial and, Speed Dial work
## without restrictions.

## when APPSTAT is set to 2, Call Log is suppressed, for Redial the
## Last-6-numbers (last-8-numbers for 4630) option is suppressed
## and changes to Speed Dial are not allowed.

## when APPSTAT is set to 3, changes to Speed Dial are not allowed.

## example:
SET APPSTAT 1
#####################################################################

###################### Option Access Settings #######################

## Use this setting to enable or disable access to certain 4610,
## 4620 and 4630 user options.

## When OPSTAT is set to 000, the user options are not accessible.
## For 4630, the Lock control is not accessible.

## When OPSTAT is set to 001, the user can only invoke the Log-Off
## Option on the 4610 and 4620. For the 4630 this setting is the
## same as 000.

## When OPSTAT is set to 010, the user can only invoke view-only options.
## The user cannot change any setting. Also for 4630, Lock control
## is not accessible,

## When OPSTAT is set to 011, the user can only invoke view-only options
## and the Log-Off Option on the 4610 and 4620. For the 4630 this setting
## is the same as 010.

## When OPSTAT is set to 100, the user can access all options except the
## view-only options and the Log-Off option on the 4610 and 4620.

## When OPSTAT is set to 101, the user options can access all options
## except the view-only options. For the 4630 this setting
## is the same as 100.

## When OPSTAT is set to 110, the user can invoke all the options except
## the Log-Off option on the 4610 and 4620. For the 4630 this setting
## is the same as 111.

## When OPSTAT is set to 111, the user can invoke any or all of the user
## options.

## example:
SET OPSTAT 111

######################################################################
####### ==== END OF 4610, 4620 and4630 IP Phone Settings ==== #######

###############################################################
########## ==== 4630 specific IP Phone Settings ==== ##########

######## Settings for the 4630 IP Phone LDAP Application ########

## These settings are used to enable and administer the LDAP
## application on the 4630.

## Your LDAP Directory server Address
## You must set this value to activate the LDAP application.
## example:
## SET DIRSRVR ldap.mycompany.com

## The TCP port number of your LDAP Directory Server
## The default port number is 389. If you wish to change the
## port number, you must set this value.
## example:
SET DIRSRVRPORT 389

## The Directory Topmost Distinguished Name
## You must set this value.
## example:
SET DIRTOPDN "ou=People,o=My Company Inc."

## The default search value. The 4630 only supports
## searches on names.
## CHANGING THIS VALUE IS NOT RECOMMENDED.
## example:
SET DIRFULLNAME cn

## The Directory Telephone Number field.
## CHANGING THIS VALUE IS NOT RECOMMENDED.
## example:
SET DIRTELNUM telephonenumber

## Directory Coding Scheme
## The valid settings are Latin-1, Ascii and Unicode
## example:
SET DIRCODING Latin-1
#####################################################################

############ Settings for 4630 IP Phone Web Application ############

## These settings are used to enable and administer the Web
## application on the 4630.

## NOTE: Avaya hosts a web site for the 4630 IP Phone.
## The WEBHOME and WEBCODING parameters are set up
## to point your 4630 IP telephones to this hosted site.
## To disable this operation, put "##" in front
## of the lines SET WEBHOME ... and SET WEBCODING ...
## To change the web site that your phones point to,
## replace the provided URL in the SET WEBHOME .. line
## with the URL of your site.

## NOTE: Your network must be using Domain Name Services
## for the Avaya hosted site settings to operate properly.

## The URL of your 4630 Home page
## example (Note: The site specified below is hosted by Avaya):
SET WEBHOME

http://support.avaya.com/elmodocs2/avayaip/4630/index.htm

## The coding to be used for characters entered in forms on web pages
## The valid settings are Latin-1, Ascii and Unicode
## example:
SET WEBCODING ASCII

## Your HTTP proxy server address (name or IP address)
## example:
## SET WEBPROXY my.proxy.company.com

## The TCP port number of your HTTP proxy server
## example:
## SET WEBPORT 80

## A list of one or more HTTP proxy server exception domains
## separated by commas without any spaces.
## Accesses to these addresses will not go through the proxy
## server.
## example:
## SET WEBEXCEPT 135.18.18.18,135.20.21.20
#####################################################################

######## 4630 Emergency Contact Number ########

## If set, this number will be the top-leftmost speed dial button in group 1
## of the 4630 speed dial screen and labeled "EMERGENCY".
## example:
SET PHNEMERGNUM 9911
#####################################################################

######## SETTINGS FOR 4630 VOICEMAIL APPLICATION ########

## VoiceMail HOME URL
#SET VMLHOME

http://voicemail.3ecompany.com

## The coding to be used for characters entered in forms on web pages
SET VMLCODING ASCII

#####################################################################
#################### 4630 Stock Ticker ##############################

## Use this setting to activate the stock ticker on your 4630. Go to
## Options on your 4630 to complete setup of this feature.
## Use 0 to Disable or 1 to Enable (Default)
## example:
SET STKSTAT 1

#####################################################################
############## End of 4630 Specific IP Phone Settings ###############

#####################################################################
############## 4610 and 4620 Specific IP Phone Settings #############

################ FTP Server for Backup/Restore ######################

## NOTE: Setting the FTP backup/restore server address here will cause
## all 4610 and 4620 IP telephones to use the same settings
## and over write each other's backup files. To use this
## feature to perform backup and restores of individual
## IP telephones, these parameters must be set individually
## at each telephone. See the LAN Administrators Guide for
## more details.

## The IP Address of your FTP Server
## example:
## SET FTPSRVR xxx.xx.xx.xx
#####################################################################

####### 4610 and 4620 IP Phone Multi-Language Administration ########

## Use this value to set the local display
## language of your 4610 and 4620.

## For all 4610SW 4620 sets, and 4620SW sets that have
## been loaded with single-byte software, use one of the
## following settings:
## For English use keyword "English"
## For French use keyword "Francais"
## For Italian use keyword "Italiano"
## For Japanese use keyword "Katakana"
## For Dutch use keyword "Nederlands"
## For German use keyword "Deutsch"
## For Portuguese use keyword "Portugues"
## For Spanish use keyword "Espanol"

## For 4620SW sets that have been loaded with multi-byte software
## to support Chinese/Russian/English fonts, use one of
## the following settings:
## For English use keyword "English"
## For Chinese use keyword "Chinese"
## For Russian use keyword "Russian"

## For 4620SW sets that have been loaded with multi-byte software
## to support Japanese/Russian/English fonts, use one of
## the following settings:
## For English use keyword "English"
## For Japanese use keyword "Japanese"
## For Russian use keyword "Russian"

## example:
SET SYSLANG English
#####################################################################

###### Settings for the 4610 and 4620 IP Phone Web Application ######

## These settings are used to enable and administer the Web
## application on the 4610 and 4620.

## NOTE: Avaya hosts a web site for the 4610 and 4620 IP Phones.
## The WMLHOME and WMLCODING parameters are set up
## to point your 4610 and 4620 IP telephones to this hosted site.
## To disable this operation, put "##" in front
## of the lines SET WMLHOME ... and SET WMLCODING ...
## To change the web site that your phones point to,
## replace the provided URL in the SET WMLHOME .. line
## with the URL of your site.

## NOTE: Your network must be using Domain Name Services
## for the Avaya hosted site settings to operate properly.

## The URL of your 4610 and 4620 Home page
## example (Note: The site specified below is hosted by Avaya):
SET WMLHOME

http://support.avaya.com/elmodocs2/avayaip/4620/home.wml

## The coding to be used for characters entered in forms on web pages
## The valid settings are Latin-1, Ascii and Unicode
## example:
SET WMLCODING ASCII

## Your HTTP proxy server address (name or IP address)
## example:
## SET WMLPROXY my.proxy.company.com

## The TCP port number of your HTTP proxy server
## example:
## SET WMLPORT 8080

## A list of one or more HTTP proxy server exception domains
## separated by commas without any spaces (IP ADDRESSES ONLY).
## Accesses to these addresses will not go through the proxy
## server.
## example:
## SET WMLEXCEPT 135.18.18.18,135.20.21.20
#####################################################################
########## End of 4610 and 4620 Specific IP Phone Settings ##########

## END OF SETTINGS SCRIPT FILE


46XXUPGRADE.TXT

####################################
#Copyright Avaya 2003 #
#All rights reserved #
####################################
#check bootApp version #
####################################
IF $MODEL4 SEQ 4602 goto BOOTAPP4602
IF $MODEL4 SEQ 4606 goto BOOTAPP46XX
IF $MODEL4 SEQ 4612 goto BOOTAPP46XX
IF $MODEL4 SEQ 4620 goto BOOTAPP4620
IF $MODEL4 SEQ 4624 goto BOOTAPP46XX
goto END
# BOOTAPP4602
IF $BOOTNAME SEQ bb4602r1_61.bin goto DEF46XX
SET APPNAME bb4602r1_61.bin
goto END
# BOOTAPP4620
IF $BOOTNAME SEQ 4620COMMON.V1719 goto DEF46XX
SET APPNAME bbla20_1719.bin
goto END
# BOOTAPP46XX
IF $BOOTNAME SEQ 46XXCOMMON.V36 goto DEF46XX
IF $BOOTNAME SEQ 46XXCOMMON.V52 goto DEF46XX
IF $BOOTNAME SEQ 46XXCOMMON.V69 goto DEF46XX
SET APPNAME bbla0_69.bin
goto END
################################
#download definity bigApp #
################################
# DEF46xx
IF $MODEL4 SEQ 4602 goto DEF4602
IF $MODEL4 SEQ 4606 goto DEF4606
IF $MODEL4 SEQ 4612 goto DEF4624
IF $MODEL4 SEQ 4620 goto DEF4620
IF $MODEL4 SEQ 4624 goto DEF4624
goto END

#definity bigApp for 4602 model
# DEF4602
SET APPNAME ap4602r1_61.bin
goto END
#definity bigApp for 4606 model
# DEF4606
SET APPNAME def06r1_73.bin
goto END
#definity bigApp for 4620 model
# DEF4620
SET APPNAME def20r1_73.bin
goto END
#definity bigApp for 4612 & 4624 model
# DEF4624
SET APPNAME def24r1_73.bin
goto END
# END
#####################################
#download the 46xx Settings script #
#####################################
GET 46xxsettings.scr
GET 46xxsettings.txt






TFTP Server Installation and Configuration

The Avaya TFTP server software is located here:

http://support.avaya.com/japple/css...ea&temp.productID=107755&temp.bucketID=108025

The installation is a standard default install, no changes were made to the installation process.

After the installation completes start the application by:

1) Go to the “Start” button
2) Select “Programs”
3) Select “TFTPSuite95Pro”
4) Start the application labeled “TFTPServer32” (This application only runs on the desktop therefore the server that is hosting this will need to remain logging in with this application running at all times.)

Once the application menu starts, select “System” and the “Setup”. Once in the configuration menu select the outbound tab and browse to the directory that contains the 46xxsettings.txt and 46xxupgrade.txt files.




Modifications to DHCP Scopes

In order to support Avaya IP phones a couple of modifications the production DHCP server was necessary.

1) Start DHCP admin
2) Right click on the DHCP server and select “Set Predefined Options”
3) Select Add
4) In the Name box type “Avaya IP Telephones”
5) In the Data Type select “String”
6) In the Code box type 176
7) Select OK
8) At the next window Under Option Name select “176 Avaya IP Telephones”
9) In the String Value Box type “mcipadd=xxx.xxx.xx.xx,mcport=1719,tftpsrvr=xxx.xxx.xx.xx”
10) Select OK
11) This scope option will need to be added to any scope that you wish to host IP phones in.




Modifications to Routing Interfaces

On any new networks that are created and will need to access a DHCP that is not on their local subnet we’ll need to add a helper address to the router so that their DHCP request will be forwarded to the DHCP server. Below are the required steps:

1) Login to the router that the local subnet terminates on. (Typically this will also be the router that is their default gateway)
2) Enter global configuration mode (Config term)
3) Ether interface configuration mode on the interface facing the clients (interface fastethernet 0/0)
4) Add a ip helper to forward DHCP UDP packets to DHCP server (ip helper-address xxx.xxx.xx.xx)
5) Exit (exit)
6) Save your config (write memory)


Modifications to VOIP Phones

The following changes need to be made to each phone:

1) Select Options (has a check mark on the button)
2) Select Page Right (right arrow)
3) Select PC Ethernet Interface
4) Select Page Right
5) Select 100 MBS Full Duplex
6) Select Save
7) Select Phone/Exit (it’s actually the button below the text)
8) Reboot the PC

 

[FortKnox]

mhypolite,

I am having exact same issue. Let me know what you find out.

 

[schned99]

Are you using a codec set with G729 for these remote phones? I have seen people set up G711 uncompressed for their main site, but the remote sites, especially if conncected via VPN tunnel, will need G729 in the codec. If you are only using one codec and it is set to G711, you can add an entry for G729 and those phones that need the compression will default down to G729.

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[mhypolite]

I was using G.711MU as the only codec set on the PBX, i have added G.729 , but still no change

 

[schned99]

Hmmmm, it looks like the phone is registering to the call server for call control, but it can't talk to the MEDPRO for the signaling/voice connection. I'm sure you already checked to make sure there where no firewall/connectivity issues for the CLAN IP address, did you check for the MEDPRO IP address also?

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[mhypolite]

Yep, from the remote end, i can ping both Clan and Medpro, i can even ping the phone from the pbx also.

 

[FortKnox]

I am sure mhypolite is experiencing the same thing I am, so I will post what happens for me:

VPN tunnel is established (using vpn router), then try to login using ip softphone (same thing occurs using a hardphone)

IP Softphone is set to Cable/Isdn (G.729 or G.723), and the vpn and port range are unchecked.


Here is the 'list trace ras':
time data
17:19:56 snd RCF endpt 192.168.223.2:1103 switch 192.168.0.50:1719 ext 899
17:19:56 rcv NSM endpt 192.168.223.2:1103 switch 192.168.0.50:1719 ext 899
17:19:56 snd NSM endpt 192.168.223.2:1103 switch 192.168.0.50:1719 ext
17:20:04 denial event 2011: IP FURQ-No Q931 msg rcvd endpt 192.168.223.2 data9
17:20:04 snd URQ endpt 192.168.223.2:1103 switch 192.168.0.50:1719 ext 899

On the vpn firewall router on the Definity's subnet, I have a vpn any/any rule called Cisco_All, and here is the traffic monitor:
09/13/05 17:19 firewalld[163]: allow out eth1 44 tcp 20 64 192.168.0.50 192.168.223.2 1720 20750 syn ack (Cisco_All)
09/13/05 17:20 firewalld[163]: allow in ipsec0 235 udp 20 127 192.168.223.2 192.168.0.255 138 138 (Cisco_All)
09/13/05 17:20 firewalld[163]: allow out eth1 98 udp 20 64 192.168.0.50 192.168.223.2 1719 1104 (Cisco_All)
09/13/05 17:20 firewalld[163]: allow out eth1 98 udp 20 64 192.168.0.50 192.168.223.2 1719 1105 (Cisco_All)
09/13/05 17:20 firewalld[163]: allow out eth1 98 udp 20 64 192.168.0.50 192.168.223.2 1719 1106 (Cisco_All)
09/13/05 17:20 firewalld[163]: allow in ipsec0 56 icmp 20 127 192.168.223.2 192.168.0.50 3 3 (Cisco_All)
09/13/05 17:20 firewalld[163]: allow out eth1 44 tcp 20 64 192.168.0.50 192.168.223.2 1720 16845 syn ack (Cisco_All)
09/13/05 17:20 firewalld[163]: allow out eth1 40 tcp 20 64 192.168.0.50 192.168.223.2 1720 20750 rst ack (Cisco_All)
09/13/05 17:21 firewalld[163]: allow out eth1 40 tcp 20 64 192.168.0.50 192.168.223.2 1720 16845 rst ack (Cisco_All)

The subnet of the Definity is 192.168.0.0 / 255.255.255.0
The subnet of the IP Softphone is 192.168.223.0 / 255.255.255.0

No firewall traffic being blocked, all other applications through the vpn work fine.

 

[FortKnox]

I did a ethereal dump if anyone is interested in looking at it.

I did a ethereal dump on the phone switch, and on the voip phone.

The phone switch's ip is 192.168.0.40 and the voip phone is 192.168.223.2

http://tinyurl.com/bdvhu

The basics of the dump just says:
H.225 RAS registrationRequest
H.225 RAS registrationConfirm
H.225 RAS nonStandardMessage

 

[schned99]

I know you guys have follow most of these proceedures already, but here is a cut and paste of the resolution proceedures from the documentation. Enjoy:

1 Has a network assessment ever been done and has the network not been modified after the
assessment?
Y. There may be a network or MedPro problem. All possibilities need to be explored, go to
Step 3.
N. The network may not be compliant with the Avaya’s network requirements. If the
problem cannot be resolved by using the steps described below, then a (re-)assessment
may need to be done, go to Step 2.

2 Look at the large pattern first: do other IP Telephones experience the same problem (assuming
multiple IP Telephones are installed)?
Y. There may be a C-LAN, a MedPro, or a network problem. All possibilities need to be
explored, go to Step 3.
N. Go to Step 3 because it could still be that the IP Telephone is the only one connected
registered with the C-LAN or only one assigned to the MedPro that has the problem.

3 Because there is a problem with many IP Telephones, is the C-LAN that the IP Telephone is
registered to operational?
a Execute the status station <extension #> command.
b Scroll to page 3 (Call Control Signaling).
In the Switch Port field look up the slot location of the C-LAN circuit pack that is
responsible for the IP Telephone, for example 07D1703.
Appendix E. Troubleshooting
No Dial Tone
IP Telephony Deployment Guide
June 2004
338
c Verify that the IP Telephone is registered properly with Communication Manager by
checking the Registration Status field on that page. If the IP Telephone is not
registered, then ensure that it is registered.
d Execute the test board 07D17 command.
This should indicate (all tests should pass) that the C-LAN board is operational according
to the software. If any test fails then refer to the Avaya Communication Manager
Hardware Maintenance Manual.
e Execute the status link command and ensure that the link is in service.
If the link is out of service, then check the Installation Manual to make sure the C-LAN
has been installed correctly.
If both the test board and the status link command do not show any problems with the C-LAN
board, then go to Step 4.

4 Because there is a problem with many IP Telephones, is the MedPro circuit pack operational?
a Go off-hook on the IP Telephone.
b Execute the status station <extension #> command.
c Scroll to page 3 (Call Control Signaling).
In the Audio Channel section if the Switch Port field contains a port location, then go
to Step d; otherwise go to Step e.
d We have a MedPro port that is dynamically allocated to the IP call. Go to page 5 of the
Station form and check the Last Tx Sequence field that shows the RTP sequence
number of the last packet sent by the MedPro to the IP Telephone. This sequence number
should increase at a regular rate when you run the status station command repeatedly. If it
does not increase, then there is likely a MedPro hardware or firmware problem. Use the
Communication Manager Maintenance Manual to resolve the issue. If packets are being
transmitted normally, then go to Step 5.
If the audio channel on the Station form is blank, this might be due to an inability of the
MedPro to allocate resource for the call.
e Execute the list measurements ip dsp-resource command to determine whether there
are sufficient MedPro resources in the system.
Check for denials, blockage and out-of-service condition. If any of those measurements
are greater than 0, this may indicate that any of the following problems might exist on the
MedPro:
• The MedPro may have run out of DSP resources. After some users will have
disconnected the problem will resolve itself. If this is a regular problem, another
MedPro board needs to be installed.
• The firmware should be FW46 or later. Replace the firmware if needed.
• One of the DSPs may be bad or there could be firmware problem. This can be
checked in the hardware error log by executing the display errors command.
Escalate the problem to the next Avaya Maintenance tier.
• Communication Manager might not be able to find a MedPro in the network
region where the IP Telephone resides.
f If there are no MedPro problems, then go to Step 5.
Appendix E. Troubleshooting
No Dial Tone
IP Telephony Deployment Guide
June 2004
339

5 Can the MedPro ping the IP Telephone?
a Execute the status station <extension #> command.
b Scroll to page 3 (Call Control Signaling).
In the Switch Port field look up the slot location of the C-LAN circuit pack that is
responsible for the IP Telephone, for example 07D1717.
c Get the IP address of the IP Telephone from the Set-end IP Addr field.
Note that hereafter, to simplify the description, it is assumed that this address is
135.9.42.105.
d Execute the ping ip-address 135.9.42.105 board 07D17 command.
Y. The MedPro receives echo replies from the IP Telephone, thus there is network
connectivity between the MedPro and the telephone. The IP Telephone might be
faulty. Replace the IP Telephone with another one to verify this. If this still does
not solve the problem, go to Step 7.
N. The IP Telephone is invisible to the MedPro. Go to Step 6.

6 Find out where the ping from the MedPro terminated.
a Execute the trace-route ip 135.9.42.105 board 07D15 command.
If network connectivity cannot be established between the MedPro and the telephone, one
hop will be delineated with “3 *.”
b Begin analyzing the network at the previous router (the last IP address displayed).

7 Are the transmission speed and transmission duplex (HDX, FDX) of the MedPro and the Ethernet
switch compatible?
a Check this by verifying the layer 1 port statistics on the Ethernet switch connected to the
MedPro.
Look for Frame check sequence errors, late collisions, and runts.
Y. Go to Step 8.
N. Change the port settings on the Ethernet switch and/or the IP Interfaces form
(change ip-interfaces) in Communication Manager to make speed and duplex
compatible.
NOTE:
If one side’s duplex is set to autonegotiate, the other side must also be set to
autonegotiate or half. Locking one side to full duplex will cause errors.
If this resolves the problem then no further steps need to be taken; otherwise go to Step 8.

8 Are the transmission speed and transmission duplex (HDX, FDX) of the IP Telephone and the
Ethernet switch compatible?
a Verify the Layer 1 port statistics on the Ethernet switch connected to the IP Telephone
(frame check sequence errors, late collisions, and runts).
NOTE:
The switch port must be set to autonegotiate or half duplex or there will be a duplex
mismatch.
Y. Go to Step 9.
N. Change the port settings to make speed and mode compatible. If this resolves
the problem then no further steps need to be taken, otherwise go to Step 9.
Appendix E. Troubleshooting
Talk path
IP Telephony Deployment Guide
June 2004
340

9 Does the C-LAN receive an off-hook indication from the IP Telephone?
a Check this by running an MST (message sequence tracer) trace for the IP Telephone.
Y. The IP Telephone at least generates messages. Go to Step 10.
N. The IP Telephone might be the problem. Replace the IP Telephone with another
IP Telephone and check if this solves the problem. If it does, then order a new IP
Telephone. If it does not solve the problem, then escalate the problem to the next
Avaya Maintenance tier.

10 There must be a network problem. Compliance with the Avaya network requirements might be an
issue as well, and a (re-)assessment may need to be done. Install a protocol analyzer in the
network to capture live traffic and analyze the network in further detail.


Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[mhypolite]

Guys, I sorted out the problem, for me I am using 2 Netscreen NS-5GT firewalls to provided the LAN to LAN VPN, I was doing some debugging and saw H.323 unknown errors, so although the ports were open netscreen was trying to interpret the traffic cause it support the H.323 application, so I edited the rules to ignore H.323 traffic and just allow it to go through, and that worked for me, the phones are now up properly.

Thanks for all the responces

 

[FortKnox]

I am still having my issue.

An Avaya guy looked at my ethereal logs, and he said that my ip phone network is send a dual request. I dont quite know what he meant, but he kept saying that I had a dual path or something. He said that something, somewhere in the vpn tunnel is echoing the registration.

I have another vpn endpoint router coming, I will try it, if it doesnt work, then the finger will point at the WatchGuard.

 

[mhypolite]

Most likely its one of your firewalls, my phones were doing the exact same thing and it was the netscreen intercepting the h.323 traffic and trying to modify it and then send it to the avaya and we ended up with an incompatibility, look for a way to tell your traffic ignore h.323 just allow the ports to pass without trying to translate it, I fond that feature on the netscreen that worked for me

 

[FortKnox]

Well, I found the problem.

I bought a D-Link model DI-804HV, created a VPN tunnel with it, and the phone registers right up without a problem.

Thereby, by process of discrimination, the problem lies in the Linksys WRV54G. Dont buy it if you plan on using it with a Definity.