Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

H.225 header incompatibility

I have a Mediatrix talking H.323 to Cisco 7960 via Cisco Call Manager v3.2.1. Cisco 7960 can establish a voice call with Mediatrix as long as Cisco initiates the call.

When Mediatrix initiates the call, Cisco reject the H.225 call setup with the following.

from Mediatrix:

Q.931

Protocol discriminator: Q.931

Call reference value length: 2

Call reference value: 3A98

Message type: SETUP (0x05)

Sending complete

Bearer capability

Information element: Bearer capability

Length: 3

Coding standard: ITU-T standardized coding

Information transfer capability: Unrestricted digital information

Transfer mode: Circuit mode

Information transfer rate: 64 kbit/s

User information layer 1 protocol: Recommendation H.221 and H.242

Display

Information element: Display

Length: 19

Display information: H.323 - 4 Ports FXS

Called party number

Information element: Called party number

Length: 5

Type of number: National number

Numbering plan: E.164 ISDN/telephony numbering

Number: 2018

User-user

Information element: User-user

Length: 348

Protocol discriminator: X.208 and X.209 coded user information

User information: 20F8060008914A000300AC749150082F...

from Cisco:

Q.931

Protocol discriminator: Q.931

Call reference value length: 2

Call reference value: BA98

Message type: RELEASE COMPLETE (0x5a)

Cause

Information element: Cause

Length: 2

Coding standard: ITU-T standardized coding

Location: User (U)

Cause value: Unallocated (unassigned) number

User-user

Information element: User-user

Length: 33

Protocol discriminator: X.208 and X.209 coded user information

User information: 2580060008914A000201110002B21F87...

Does anyone know based on this trace which part of the header is not accepted by Cisco? The called number should be valid.

Gaston

1 REPLY
Cisco Employee

Re: H.225 header incompatibility

If the number 2018 is a valid dialable number on the CallManager system, then you have probably not granted the proper Calling Search Space for the gateway to be able to call that number.

259
Views
0
Helpful
1
Replies
CreatePlease to create content