noneStandardIdentifier over MPLS 1

[kholladay]

Has anyone seen this? We have a MPLS between the two sites with an Adtran at one site and a Cisco router at the other. This is showing "nonStandardIdentifier" and the phone cannot register.


1377081mS RasRx: v=IFace=LAN1, Src=172.16.2.223:49300, Dst=172.16.162.240:1719 peb=0
RasMessage = gatekeeperRequest = {
requestSeqNum = 2
protocolIdentifier = 0.0.8.2250.0.5
nonStandardData = {
nonStandardIdentifier = object = 2.16.840.1.113778.4.2.1
data =
85 01 40 ..@
}
rasAddress = ipAddress = {
ip =
ac 10 02 df ....
port = 49300
}
endpointType = {
terminal = {
}
mc = false
undefinedNode = false
}
endpointAlias = { 1 item(s)
[0] = dialedDigits =
32 30 31 34 2014
}
tokens = { 1 item(s)
[0] = {
tokenOID = 2.16.840.1.114187.1.6.2
dhkey = {
halfkey =
6d fa 3f 09 7b 18 eb 3f 91 0c f1 1e 60 0c 3e 62 m.?.{..?....`.>b
29 d5 a7 f4 24 57 82 0a 55 d8 00 ed 51 80 be 88 )...$W..U...Q...
cf 70 b7 64 06 12 cd 60 17 12 c1 fb c4 89 75 1f .p.d...`......u.
dd 8d 74 eb 40 44 60 d8 8a 37 26 45 16 83 9d b3 ..t.@D`..7&E....
46 ac a1 b1 a4 ab 07 c9 0a 39 ef 72 f4 c6 31 7a F........9.r..1z
90 b7 28 ea 6a 39 72 c2 bc 13 1d a6 d7 a9 00 06 ..(.j9r.........
dd 08 de bb 86 25 4b 3a 59 4a 4d 0a fd 89 50 c2 .....%K:YJM...P.
aa 27 1f 9e d3 e2 3f 5c b4 c5 95 79 de bb 18 b5 .'....?\...y....
modSize = empty
generator = empty
}
profileInfo = { 2 item(s)
[0] = {
elementID = 2
element = octets =
ba d1 30 63 ..0c
}
[1] = {
elementID = 1
element = octets =
d0 c3 00 00 d0 c3 00 00 d0 c3 00 08 ............
}
}
}
}
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 = { 2 item(s)
[0] = {
id = oid = 2.16.840.1.114187.1.10
parameters = { 10 item(s)
[0] = {
id = standard = 4
}
[1] = {
id = standard = 5
}
[2] = {
id = standard = 6
}
[3] = {
id = standard = 7
}
[4] = {
id = standard = 10
}
[5] = {
id = standard = 11
}
[6] = {
id = standard = 12
}
[7] = {
id = standard = 13
}
[8] = {
id = standard = 14
}
[9] = {
id = standard = 15
}
}
}
[1] = {
id = oid = 2.16.840.1.114187.1.9
parameters = { 2 item(s)
[0] = {
id = standard = 1
content = number8 = 1
}
[1] = {
id = standard = 4
content = bool = true
}
}
}
}
}
}
NonStandardDataMessage = discoveryRequest = {
natTerminal
}


Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[hairlessupportmonkey]

is the cisco got any inspect maps enabled?

ACSS - SME
General Geek

 

[amriddle01]

Sure does look like something is interfering with the traffic

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[Bas1234]

You could check the following in the cisco;

no inspect h323 h225
no inspect h323 ras

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[kholladay]

First thing I thought as well but these are managed routers with no firewalls enabled. They claim there are no inspect policies enabled.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[hairlessupportmonkey]

something is messing with the packets then.

perhaps fragmentaion.... somethings MTU / MSS size isnt set.

also, the routers, ask them to fix them to 100Mbit / full instead of Auto on the NIC.

ACSS - SME
General Geek

 

[Westi]

Hi Kyle
if you say

They claim there are no inspect policies enabled[/Quote kholladay] does that mean you need to rely on other people for the programming?
have them send you a config of the Cisco in text format and have a look for yourself. I know people don't like to do that but that might show some anomalies in the programming.

Joe W.

16103

 

[kholladay]

Yes they are telepacific provided/managed routers. I've sent them the traces and asked for the configs. There is a huge amount of jitter and packet loss on the span when using ping that they are trying to blame on the fact that ICMP is in the low priority queue. But, since there is no other traffic on the span yet, the low priority queue is the only one with traffic so I can't see how that can be the case.

Kyle Holladay
ACSS & APSS SME Communications
MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"I have one speed, I have one gear...GO!!!" - Charlie Sheen

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[mattKnight]

>But, since there is no other traffic on the span yet, the low >priority queue is the only one with traffic so I can't see how >that can be the case.

You are assuming that only congestion on your access circuit will cause packets to be dropped. If they carrier has congestion elsewhere in its cloud, your low priority ICMP will be dropped over someobe else's AF31 traffic.

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.

 

[hairlessupportmonkey]

also, what happens if you put your own firewalls either side and create a tunnel - does it stay up?

ACSS - SME
General Geek