We are trying to connect a NEC Aspire phone system to a Avaya Definity system with T1 Point-to-point using H.323.
We are getting close but when we call from the Nec to the Definity it will give us a busy signal and if we watch the traffic.
Nec --> TCP hostcall
Definity -->TCP hostcall ACK
Nec -->TCP hostcall Ack
Nec -->TCP TCP segment of a reassembled PDU
Nec --> H.225.0 CS:Setup OpenLogicalChannel
Definity -->TCP Hostcall ACK
Definity -->H.225.0 cs:CallProceeding
Q.931
Protocol discriminator: Q.931
Call reference value length: 2
Call reference flag: Message sent to originating side
Call reference value: 0001
Message type: CALL PROCEEDING (0x02)
User-user
Information element: User-user
Length: 92
Protocol discriminator: X.208 and X.209 coded user information
H.225.0 CS
H323-UserInformation
h323-uu-pdu
h323-message-body: callProceeding (1)
callProceeding
protocolIdentifier: 0.0.8.2250.0.2 (Version 2)
destinationInfo
vendor
vendor
t35CountryCode: United States (181)
t35Extension: 0
manufacturerCode: 19540
H.221 Manufacturer: Lucent Technologies (0xb5004c54)
productId: Avaya Definity
versionId: R009i.05.1.122.4
gatekeeper
gateway
protocol: 3 items
Item 0
SupportedProtocols: h320 (2)
h320
supportedPrefixes: 1 item
Item 0
SupportedPrefix
prefix: dialedDigits (0)
dialedDigits: 9
Item 1
SupportedProtocols: h323 (5)
h323
supportedPrefixes: 1 item
Item 0
SupportedPrefix
prefix: dialedDigits (0)
dialedDigits: 9
Item 2
SupportedProtocols: voice (7)
voice
supportedPrefixes: 1 item
Item 0
SupportedPrefix
prefix: dialedDigits (0)
dialedDigits: 9
mcu
..1. .... mc: True
...0 .... undefinedNode: False
callIdentifier
guid: 00408139-9f4b-4212-a5e1-000000000000
Nec --> Q.931 Status
Q.931
Protocol discriminator: Q.931
Call reference value length: 2
Call reference flag: Message sent from originating side
Call reference value: 0001
Message type: STATUS (0x7d)
Cause
Information element: Cause
Length: 3
.... 0000 = Cause location: User (U) (0)
.00. .... = Coding standard: ITU-T standardized coding (0x00)
1... .... = Extension indicator: last octet
.110 0100 = Cause value: Invalid information element contents (100)
1... .... = Extension indicator: last octet
Information element: User-user
Call state
Information element: Call state
Length: 1
.00. .... = Coding standard: ITU-T standardized coding (0x00)
Call state: Call initiated
Definity --> H.225.0 CS: alerting openlogicalchannel
Definity -->RTCP Sender Report Source description
Definity -->RTC PT=ITU-T G.711 PCMU
Nec --> Q.931 Status
Q.931
Protocol discriminator: Q.931
Call reference value length: 2
Call reference flag: Message sent from originating side
Call reference value: 0001
Message type: STATUS (0x7d)
Cause
Information element: Cause
Length: 3
.... 0000 = Cause location: User (U) (0)
.00. .... = Coding standard: ITU-T standardized coding (0x00)
1... .... = Extension indicator: last octet
.110 0100 = Cause value: Invalid information element contents (100)
1... .... = Extension indicator: last octet
Information element: User-user
Call state
Information element: Call state
Length: 1
.00. .... = Coding standard: ITU-T standardized coding (0x00)
Call state: Call initiated
Definity -->RTCP Sender Report Source description
Definity -->RTC PT=ITU-T G.711 PCMU
Definity -->RTCP Sender Report Source description
Definity -->RTC PT=ITU-T G.711 PCMU
the definity goes on for a couple pages of the same packet until the Nec end the call
Nec --> H.225.0 CS: releaseComplete
Q.931
Protocol discriminator: Q.931
Call reference value length: 2
Call reference flag: Message sent from originating side
Call reference value: 0001
Message type: RELEASE COMPLETE (0x5a)
Cause
Information element: Cause
Length: 5
.... 0000 = Cause location: User (U) (0)
.00. .... = Coding standard: ITU-T standardized coding (0x00)
1... .... = Extension indicator: last octet
.110 0110 = Cause value: Recovery on timer expiry (102)
1... .... = Extension indicator: last octet
Timer: 303
User-user
Information element: User-user
Length: 38
Protocol discriminator: X.208 and X.209 coded user information
H.225.0 CS
H323-UserInformation
h323-uu-pdu
h323-message-body: releaseComplete (5)
releaseComplete
protocolIdentifier: 0.0.8.2250.0.2 (Version 2)
callIdentifier
guid: 00408139-9f4b-4212-a5e1-000000000000
presentationIndicator: addressNotAvailable (2)
addressNotAvailable: NULL
screeningIndicator: userProvidedNotScreened (0)
0... .... h245Tunneling: False
to me it looks like the Nec does not like one of the information Elements that the Definity is sending. the Definity continue with the call until the Nec times out.
both of our vendors are stumped Please if anyone could give me any suggestion that would help.
