×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX
2

Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
Dear Members,

I have IPO R 7.0.12 installed with IP Endpoint License.
I want to register Remote IP Phone at Home to this IPO.
That phone is registering in Local LAN but from far end i have an issue.
It is discovering my public IP which is static.
Please find below trace which i am getting in IPO Monitor.


371396mS RasRx: v=IFace=LAN1, Src=10.10.62.213:26816, Dst=192.168.42.42:1719 peb=0
RasMessage = gatekeeperRequest = {
requestSeqNum = 35
protocolIdentifier = 0.0.8.2250.0.2
nonStandardData = {
nonStandardIdentifier = object = 2.16.840.1.113778.4.2.1
data =
85 01 40 ..@
}
rasAddress = ipAddress = {
ip =
c0 a8 2a f2 ..*.
port = 49303
}
endpointType = {
terminal = {
}
mc = false
undefinedNode = false
}
endpointAlias = { 1 item(s)
[0] = dialedDigits =
38 36 30 30 8600
}
tokens = { 1 item(s)
[0] = {
tokenOID = 2.16.840.1.114187.1.6.2
dhkey = {
halfkey =
ea 83 bc a3 e0 3c 38 fc 28 2a 33 78 76 ed 1d b3 .....<8.(*3xv...
4d 46 12 49 15 c2 58 88 c2 73 98 34 41 03 2f 65 MF.I..X..s.4A./e
f7 7f 67 6e 1b 2f c9 d1 1d b5 49 29 40 43 85 15 ..gn./....I)@C..
f5 6e a8 8f b6 7c c2 4b c6 b1 fb aa 12 dd ef a1 .n...|.K........
02 d4 dc 9c 87 d5 51 99 f7 3a 7a c6 29 11 98 ee ......Q..:z.)...
83 0e eb 7b de d4 82 a1 72 06 90 70 ef 8f bd 7d ...{....r..p...}
73 1e de 04 74 d0 e5 c6 99 c0 21 35 f2 7a 20 da s...t.....!5.z .
59 a9 62 83 1f f5 56 c0 cb db c7 d4 9b 44 a2 5f Y.b...V......D._
modSize = empty
generator = empty
}
profileInfo = { 2 item(s)
[0] = {
elementID = 2
element = octets =
00 00 09 c8 ....
}
[1] = {
elementID = 1
element = octets =
03 e8 00 00 32 4d 00 00 55 05 03 e9 ....2M..U...
}
}
}
}
authenticationCapability = { 2 item(s)
[0] = pwdSymEnc
[1] = keyExch = 2.16.840.1.114187.1.6.2
}
algorithmOIDs = { 2 item(s)
[0] = 1.3.14.3.2.6
[1] = 2.16.840.1.114187.1.3
}
featureSet = {
replacementFeatureSet = false
supportedFeatures = { 1 item(s)
[0] = {
id = oid = 2.16.840.1.114187.1.10
parameters = { 8 item(s)
[0] = {
id = standard = 5
}
[1] = {
id = standard = 9
}
[2] = {
id = standard = 10
}
[3] = {
id = standard = 11
}
[4] = {
id = standard = 13
}
[5] = {
id = standard = 14
}
[6] = {
id = standard = 15
}
[7] = {
id = standard = 16
}
}
}
}
}
}
NonStandardDataMessage = discoveryRequest = {
natTerminal
}

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

Is this a VPN phone or you are using port forwarding?
If port fwding, you will need to enable remote ext on that interface. And create a default IP route.

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

Remote H.323 Extensions are only supported on 96xx phones.

"Trying is the first step to failure..." - Homer

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
But we are receiving request from 16XX phone.
In Monitor it is showing and also auto create user/extn is automatically created in IPO Manager.

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
This is not VPN phone.
I am using port forwarding in both the routes.
At home and also at office. I have configured DMZ.

Office Network
IPO LAN :- 192.168.42.42
Router IP :- 192.168.42.222 (LAN)
Public Static IP :- 122.170.12.218

Home Network
IP Phone LAN :- 192.168.42.242
Router IP :- 192.168.42.100

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
Please find below trace from IPO Monitor


4691022mS H323Evt: Recv GRQ from 0a0a3ed5
4691022mS H323Evt: e_H225_AliasAddress_dialedDigits alias
4691022mS H323Evt: found number <8600>
4691023mS RasTx: v=Src=192.168.42.42:1719, Dst=192.168.42.242:49307 peb=0
RasMessage = gatekeeperConfirm = {
requestSeqNum = 19
protocolIdentifier = 0.0.8.2250.0.5
gatekeeperIdentifier =
0044 0050 0054 0050 004c 0020 0044 0045 DPTPL DE
004d 004f 0020 0052 0037 MO R7
rasAddress = ipAddress = {
ip =
c0 a8 2a 2a ..**
port = 1719
}
authenticationMode = pwdSymEnc
tokens = { 1 item(s)
[0] = {
tokenOID = 0.0
timeStamp = 4669807
random = 16197
generalID =
0044 0045 0046 0049 004e 0049 0054 0059 DEFINITY
}
}
algorithmOID = 1.3.14.3.2.6
featureSet = {
replacementFeatureSet = true
supportedFeatures = { 1 item(s)
[0] = {
id = oid = 2.16.840.1.114187.1.10
parameters = { 3 item(s)
[0] = {
id = standard = 13
}
[1] = {
id = standard = 14
}
[2] = {
id = standard = 15
}
}
}
}
}
}

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

It has no problem to send requests, the question is will it get anything back and be able to handle being a remote extension.
This was most likely never put in the 16xx firmware.

Documentation also clearly states that only 9600 series phones are supported as H.323 remote extensions.
Try one of those an see what happens, if it works on the same setup you know it's the phone.

"Trying is the first step to failure..." - Homer

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

it also looks like you have the Office and LAN at home on the same subnet. i would change the home network just in case. they should not be the same.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Vive Communications

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

It doesn't matter for remote extensions if both sides are have the same internal network addresses as all communication is made against the external IPs, but the firmware of the 16xx aren't made to handle this.

"Trying is the first step to failure..." - Homer

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

I can see in the trace that the destination Addrss is 192.168.42.242 which is a private IP and can not be routed over the internet. There is a NAT issue here.

Do you have remote extension enabled on lan1? Did you set the public IP in “lan1>>public ip tab”?
Did you assign the remote user a remote profile (teleworker)?

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
Actually i am using R7. So in R7 there is no settings like remote H.323 Extn enable.
Other thing is I have 9621G and that phone also shows same error while registering from home network.
Is there any router or networking setting or ports to be allowed. Currently i did DMZ in office router to IPO LAN1

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

What about the rest of the questions? You don’t see them in the IPO config too?

Port 1719 and 1720 udp/tcp should be forwarded to the IPO. For RTP ports, you will find the range in the lan1 tab.

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
All ports are forwarded.
1718,1719,1720 TCP&UDP
49152 to 53246 TCP

All these ports are forwarded.
Additionally in network topology Open Internet selected and Public IP entered as well.

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

You need at least R8 to be able to use H.323 Remote Extensions.

Also the 49152 to 53246 port range shouldn't be open from external destinations since these include exploitable ports, this is why the default port range was later changed to 46750-50750 for IP500 and 40750-50750 for SE.

"Trying is the first step to failure..." - Homer

RE: Registration Issue in Avaya IPO R7 from Remote End IP Phone 16XX

(OP)
Okk
Thanks a lot for your valuable suggestions

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close