Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP office Networking problem

Status
Not open for further replies.

techman63

Programmer
Joined
Aug 20, 2004
Messages
47
Location
US
I have 2 IP offices networking together thru MPLS with no firewall according to the IT department. One IP office is R7.12 and other is 6.1(5) it will be upgraded to R7 next week.
The setup like this each IPO connected to the customer LAN thru LAN 1 and to the MPLS thru WAN (LAN2) on a VLAN .if I try to call the other extension is will say Unobtainable and it will display the name of the person I’m calling on the other side.
In monitor the SCN shows the other location is up and display how many users and hunt group per SCN.and in the VMP it will display the users and HG for the remote location.
I created a Route on each IP office 0.0.0.0, 0.0.0.0 and the corresponding gateway for each location and Dest LAN 2.
I can ping each location no problem .I also created a short code to dial a user on the other side and still the same results, did not work.
In monitor trace it has

238844516mS RES: Thu 23/6/2011 13:39:08 FreeMem=63632076(1) CMMsg=6 (8) Buff=200 936 874 7423 5 Links=13365
238844516mS RES2: IP 500 V2 7.0(12) Tasks=44 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=60 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=1 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
238845651mS H323Evt: V6 on the other side of line 17 tcp f52975f8 shared_tcp 0 tcp f52975f8 shared_msg_sent 0 new_caps f ver_major 6
238845651mS H323Evt: H323 stack for line 17 is connected
238845651mS H323Evt: H323Pipe::ConnectIndication cap 1
238845651mS H323Evt: H323Pipe::ConnectIndication cap 2
238845651mS H323Evt: H323Pipe::ConnectIndication cap f
238845652mS H323Evt: Shared TCP became operational for line 17
238845652mS H323Tx: dst=192.168.10.50:12040
H323 Pcol=0D(UNK) Reflen=0 ref=1F01(Remote)
0000 0d 00 1f 01 01 00 00 00 0f 00 00 00 07 00 00 00 ................
0010 00 00 00 00 0c 49 50 20 35 30 30 20 56 32 00 .....IP 500 V2.
238857521mS CMExtnEvt: DHernandez: No user activity
238858386mS PRN: WhoIsTCPSession: created
238858392mS PRN: WARNING:
238858393mS PRN: Whois - can't get access to binary file: A:\system\primary\nadcpaV1.bin!
238858393mS PRN:
238858516mS RES: Thu 23/6/2011 13:39:22 FreeMem=63628248(1) CMMsg=6 (8) Buff=200 938 874 7423 5 Links=13365
238858516mS RES2: IP 500 V2 7.0(12) Tasks=44 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=60 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=1 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
238858592mS CMExtnEvt: RReinoso: No user activity
238858789mS PRN: WARNING:
238858789mS PRN: Whois - can't get access to binary file: A:\system\primary\nadcpaV1


238905682mS H323Evt: Shared tcp socket for line 17 disconnected
238905682mS H323Evt: H323Pipe::DisconnectIndication cap 1
238905682mS H323Evt: H323Pipe::DisconnectIndication cap 2
238905682mS H323Evt: H323Pipe::DisconnectIndication cap f
238905682mS H323Evt: H323 stack for line 17 is disconnected
238906016mS RES: Thu 23/6/2011 13:40:10 FreeMem=63651236(1) CMMsg=6 (8) Buff=200 938 873 7423 5 Links=13374
238906016mS RES2: IP 500 V2 7.0(12) Tasks=44 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=60

Line 17 is the IP trunks between the systems.

I’m not sure what is that exactly mean, but to me it looks like it’s up and down and its either networking issue or a routing problems in the IP office.
I appreciate the insight on this one, the customer is giving me grief, first the VM PRO 7.19 clipping the messages and now I cant get the SCN up and running and I sent the Config fie to Catalyst support and they nothing wrong with it and they recommended to open a ticket with Avaya or try to upgrade the other system to R7 despite theoretically it should work between 6&7.
Any ideas I’m listening and thanks for sharing.

 
One system has a combo card(10 VCM resources) and other has VCM 32.
Come to think about it a bit do I need to create another route to route Between LAN1 and LAN 2.
 
>Come to think about it a bit do I need to create another route to route Between LAN1 and LAN 2.

You shouldn't need to - both networks are directly connected so the IPO should know what to do.

What sort of handsets? I'd also check that the MPLS routers are not doing any funky packet inspection of H323.

I'd also turn off and try ye olde style shortcodes for routing calls and see if that helps (as a test measure)

Try to post a trace of calls being made - that will show more than the initialisation of teh trunks



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.
 
According to the provider of the MPLS, there nothing and there is no firewall and everything is open and they can see h323 traffic.

In one side all digital phones 9504 and the other side is IP phones 9620 and analog sets.
The whole issue appears in these lines
238905682mS H323Evt: Shared tcp socket for line 17 disconnected
238905682mS H323Evt: H323Pipe::DisconnectIndication cap 1
238905682mS H323Evt: H323Pipe::DisconnectIndication cap 2
238905682mS H323Evt: H323Pipe::DisconnectIndication cap f
238905682mS H323Evt: H323 stack for line 17 is disconnected
I have monitor and system status open on both systems, if I make a call at this time it won’t go thru, but if I hit it when the lines like the following, the calls will ring the analog set but I can not test the IP set at this time ,not logged in.

238845651mS H323Evt: H323 stack for line 17 is connected
238845651mS H323Evt: H323Pipe::ConnectIndication cap 1
238845651mS H323Evt: H323Pipe::ConnectIndication cap 2
238845651mS H323Evt: H323Pipe::ConnectIndication cap f
238845652mS H323Evt: Shared TCP became operational for line 17

Line 17 is the IP trunk, and I tried with and without (allow direct media path).
That’s why I feel it’s either a network or routing issue.
Here is a long monitor trace while calling, thanks for your time.

multipleCalls = false
maintainConnection = false
}
h245Tunneling = true
}
}
905666mS H323Evt: v=0 stacknum=17 State, new=Proceeding, old=Initiated id=1102
905676mS H323Rx: src=192.168.10.50:4158
H323 Pcol=08(Q931) Reflen=2 ref=0005(Local)
Message Type = Alerting
InformationElement = CUG
0000 47 09 e4 43 6f 6e 66 31 00 02 00 G..Conf1...
InformationElement = CUG
0000 47 13 e5 43 6f 6e 66 65 72 65 6e 63 65 20 52 6d G..Conference Rm
0010 20 31 00 02 00 1...
InformationElement = CUG
0000 47 0a e6 64 64 65 64 04 31 32 35 31 G..dded.1251
InformationElement = CUG
0000 47 1b e7 06 00 65 00 6e 00 75 08 20 06 0f 00 03 G....e.n.u. ....
0010 31 00 00 00 20 f8 07 b2 92 a0 85 0c 05 1... ........
InformationElement = UU
0000 7e 00 90 05 23 80 06 00 08 91 4a 00 05 22 c0 b4 ~...#.....J.."..
0010 00 2a 00 08 49 50 20 35 30 30 20 56 32 06 36 2e .*..IP 500 V2.6.
0020 31 20 28 35 29 01 b1 c0 00 11 00 5d 04 7e 80 b9 1 (5)......].~..
0030 b4 11 d9 85 31 00 e0 07 06 0c d7 3b 02 1a 00 00 ....1......;....
0040 7f 0c 60 13 80 12 1f 00 01 00 c0 a8 0a 32 c0 00 ..`..........2..
0050 00 c0 a8 0a 32 c0 01 00 1e 40 00 7f 06 04 01 00 ....2....@......
0060 4c 60 13 80 12 1f 00 01 00 c0 a8 0a 32 c0 00 00 L`..........2...
0070 c0 a8 0a 32 c0 01 00 01 00 01 00 11 80 13 01 11 ...2............
0080 60 00 01 10 39 23 00 01 01 07 00 20 43 6f 6e 66 `...9#..... Conf
0090 31 01 80 1..
UserInformation = {
h323-uu-pdu = {
h323-message-body = alerting = {
protocolIdentifier = 0.0.8.2250.0.5
destinationInfo = {
vendor = {
vendor = {
t35CountryCode = 180
t35Extension = 0
manufacturerCode = 10752
}
productId =
49 50 20 35 30 30 20 56 32 IP 500 V2
versionId =
36 2e 31 20 28 35 29 6.1 (5)
}
terminal = {
}
mc = false
undefinedNode = false
}
callIdentifier = {
guid =
5d 04 7e 80 b9 b4 11 d9 85 31 00 e0 07 06 0c d7 ].~......1......
}
fastStart = { 2 item(s)
[0] =
00 00 7f 0c 60 13 80 12 1f 00 01 00 c0 a8 0a 32 ....`..........2
c0 00 00 c0 a8 0a 32 c0 01 00 ......2...
[1] =
40 00 7f 06 04 01 00 4c 60 13 80 12 1f 00 01 00 @......L`.......
c0 a8 0a 32 c0 00 00 c0 a8 0a 32 c0 01 00 ...2......2...
}
multipleCalls = false
maintainConnection = false
}
h4501SupplementaryService = { 1 item(s)
[0] =
60 00 01 10 39 23 00 01 01 07 00 20 43 6f 6e 66 `...9#..... Conf
31 1
}
h245Tunneling = true
}
}
fastStart[0] = {
forwardLogicalChannelNumber = 128
forwardLogicalChannelParameters = {
dataType = audioData = g711Ulaw64k = 20
multiplexParameters = h2250LogicalChannelParameters = {
sessionID = 1
mediaChannel = unicastAddress = iPAddress = {
network =
c0 a8 0a 32 ...2
tsapIdentifier = 49152
}
mediaGuaranteedDelivery = false
mediaControlChannel = unicastAddress = iPAddress = {
network =
c0 a8 0a 32 ...2
tsapIdentifier = 49153
}
mediaControlGuaranteedDelivery = false
silenceSuppression = false
}
}
}
fastStart[1] = {
forwardLogicalChannelNumber = 128
forwardLogicalChannelParameters = {
dataType = nullData
multiplexParameters = none
}
reverseLogicalChannelParameters = {
dataType = audioData = g711Ulaw64k = 20
multiplexParameters = h2250LogicalChannelParameters = {
sessionID = 1
mediaChannel = unicastAddress = iPAddress = {
network =
c0 a8 0a 32 ...2
tsapIdentifier = 49152
}
mediaGuaranteedDelivery = false
mediaControlChannel = unicastAddress = iPAddress = {
network =
c0 a8 0a 32 ...2
tsapIdentifier = 49153
}
mediaControlGuaranteedDelivery = false
silenceSuppression = false
}
}
}
905676mS H323Evt: v=0 stacknum=17 State, new=Delivered, old=Proceeding id=1102
906810mS H323Evt: RTP(50t): 192.168.12.79/49152 192.168.10.50/49152 CODEC=Ulaw64K(5) PKTSZ=160 RFC2833=off AGE=1126 SENT=50 (avg size=160) RECV=57 (avg size=160)
928574mS H323Evt: RTP(END): 192.168.12.79/49152 192.168.10.50/49152 CODEC=Ulaw64K(5) PKTSZ=160 RFC2833=off AGE=22890 SENT=1137 RECV=1145 RTdelay=0 jitter=0 loss=0 remotejitter=0 remoteloss=0
928577mS H323Tx: dst=192.168.10.50:4158
H323 Pcol=08(Q931) Reflen=2 ref=0005(Remote)
Message Type = Facility
InformationElement = UU
0000 7e 00 3b 05 26 80 06 00 08 91 4a 00 05 63 e0 70 ~.;.&.....J..c.p
0010 00 11 00 5d 04 7e 80 b9 b4 11 d9 85 31 00 e0 07 ...].~......1...
0020 06 0c d7 12 02 07 00 00 7f 06 04 01 00 08 40 00 ..............@.
0030 7f 06 04 01 00 04 01 00 01 00 10 80 01 80 ..............
UserInformation = {
h323-uu-pdu = {
h323-message-body = facility = {
protocolIdentifier = 0.0.8.2250.0.5
reason = undefinedReason
callIdentifier = {
guid =
5d 04 7e 80 b9 b4 11 d9 85 31 00 e0 07 06 0c d7 ].~......1......
}
fastStart = { 2 item(s)
[0] =
00 00 7f 06 04 01 00 .......
[1] =
40 00 7f 06 04 01 00 04 @.......
}
multipleCalls = false
maintainConnection = false
}
h245Tunneling = true
}
}
fastStart[0] = {
forwardLogicalChannelNumber = 128
forwardLogicalChannelParameters = {
dataType = nullData
multiplexParameters = none
}
}
fastStart[1] = {
forwardLogicalChannelNumber = 128
forwardLogicalChannelParameters = {
dataType = nullData
multiplexParameters = none
}
reverseLogicalChannelParameters = {
dataType = nullData
}
}
928578mS H323Tx: dst=192.168.10.50:4158
H323 Pcol=08(Q931) Reflen=2 ref=0005(Remote)
Message Type = Facility
InformationElement = UU
0000 7e 00 0e 05 28 10 01 00 10 c0 01 80 04 01 02 4a ~...(..........J
0010 40 @
UserInformation = {
h323-uu-pdu = {
h323-message-body = empty
h245Tunneling = true
h245Control = { 1 item(s)
[0] =
4a 40 J@
}
}
}
928578mS H323Evt: v=0 stacknum=17 State, new=ReleaseReq, old=Delivered id=1102
928578mS H323Tx: dst=192.168.10.50:4158
H323 Pcol=08(Q931) Reflen=2 ref=0005(Remote)
Message Type = ReleaseComplete
InformationElement = CAUSE
0000 08 02 80 90 ....
InformationElement = UU
0000 7e 00 22 05 25 80 06 00 08 91 4a 00 05 11 00 11 ~.".%.....J.....
0010 00 5d 04 7e 80 b9 b4 11 d9 85 31 00 e0 07 06 0c .].~......1.....
0020 d7 10 80 01 80 .....
UserInformation = {
h323-uu-pdu = {
h323-message-body = releaseComplete = {
protocolIdentifier = 0.0.8.2250.0.5
callIdentifier = {
guid =
5d 04 7e 80 b9 b4 11 d9 85 31 00 e0 07 06 0c d7 ].~......1......
}
}
h245Tunneling = true
}
}
928579mS H323Evt: v=0 stacknum=17 State, new=NullState, old=ReleaseReq id=1102
928596mS H323Evt: Shared tcp socket for line 17 disconnected
928596mS H323Evt: H323Pipe::DisconnectIndication cap 1
928596mS H323Evt: H323Pipe::DisconnectIndication cap 2
928596mS H323Evt: H323Pipe::DisconnectIndication cap f
928596mS H323Evt: H323 stack for line 17 is disconnected
943596mS H323Tx: dst=192.168.10.50:1720
H323 Pcol=0D(UNK) Reflen=0 ref=1F01(Remote)
0000 0d 00 1f 01 01 00 00 00 0f 00 00 00 07 00 00 00 ................
0010 00 00 00 00 0c 49 50 20 35 30 30 20 56 32 00 .....IP 500 V2.
943600mS H323Evt: V6 on the other side of line 17 tcp f5161974 shared_tcp f5274188 tcp f5161974 shared_msg_sent 0 new_caps f ver_major 6
943614mS H323Evt: V6 on the other side of line 17 tcp f5274188 shared_tcp f5274188 tcp f5274188 shared_msg_sent 1 new_caps f ver_major 6
943614mS H323Evt: H323 stack for line 17 is connected
943614mS H323Evt: H323Pipe::ConnectIndication cap 1
943614mS H323Evt: H323Pipe::ConnectIndication cap 2
943614mS H323Evt: H323Pipe::ConnectIndication cap f
943614mS H323Evt: Shared TCP became operational for line 17
943648mS H323Evt: Shared tcp socket for line 17 disconnected
943648mS H323Evt: H323Pipe::DisconnectIndication cap 1
943648mS H323Evt: H323Pipe::DisconnectIndication cap 2
943648mS H323Evt: H323Pipe::DisconnectIndication cap f
943648mS H323Evt: H323 stack for line 17 is disconnected

 
you have the networking license installed and valid on both systems?

Joe W.

FHandw, ACSS

16184
 
Yes.The SCN is active in Monitor
 
The SCN active means that the avrip packages go through on port 50795 but there are many other things that the connection needs to do.
Do you see the line being occupied and the timer going back to 0 or is it just simply ignoring the call attempt? if the timer resets then your system tries to call out correctly.
If you have another IPO (an old 406 is the best for that because you don't need licensing on them for basic SCN) then hook it up make a new IP trunk and point it to the test unit. If it works then tell the networking guys that they need to fix it. I have never experienced the IP Office to be the roblem if it was programmed correctly but had enough IT or network guys telling me that their network is OK.
Also ask them if they have Cisco routers between and if they have h.323 fixups disabled.

Joe W.

FHandw, ACSS

16184
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top