Avaya Definity H323 implementation. 1

[probe123]

I am trying to decode the H323 signaling information
sent to my IP telephone connected to an Avaya Definity
G3Si switch, I see only INFORMATION messages on
the port 1720 (over TCP), I dont see any Call setup and Call
clearing Q931 messages on this port, do they use some other
TCP port for this, is this port number negotiated with
the gatekeeper at the begining.Is there any document
available on the web for this switch which explains this.

 

[ctr999]

The Administration for Network Connectivity Manual is probably one you want to look at. You can download the R9 version of it from this link:

support.avaya.com/japple/css/japple?temp.groupID=107529&temp.selectedFamily=107557&temp.selectedProduct=107602&temp.selectedBucket=all&temp.feedbackState=askForFeedback&temp.documentID=132043&temp.selectedRelease=132274&PAGE=avaya.css.PDDocDetail&aClass=japple.web.services.DataTransactionService(runStatement,avaya.css.UsageUpdate)


Here is the link for all ECS documentation:

support.avaya.com/japple/css/japple?PAGE=avaya.css.PDProductRelease&temp.groupID=107529

 

[probe123]

Hi,
Thanks for the web site, I looked at the documents, but
could not find any reference to H323 Protocol
implementation, I am trying to analyze the data coming
to/from my IP phone, could not see any call signaling
messages on port 1720 (TCP).I can see the Q931 signalling
messages on the same port when connected to Netmeeting.
Any help is very much appreciated.
Thanks.

 

[telcoguy]

Be careful where you look,
The call setup runs over the C-lan not the MEDPRO board,
so if you watch the IP stream of the MEDPRO, you are correct, you will not be able to see the call-control data.

 

[VOIPeng]

Here are the ports to watch for and what they do. You have to keep in mind that the CLAN is the destination address for all registration and call control packets. And the Medpro or an IP phone will be the destination of the Audio Stream packets.

Port Type Description
80 Static TCP HTTP Interface (Optional)
389 Static TCP ILS Registration (LDAP)
522 Static TCP User location Service
1503 Static TCP T.120
1718 Static TCP Gatekeeper Discover
1719 Static TCP Gatekeeper RAS
1720 Static TCP H.323 Call Setup
1731 Static TCP Audio Call Control
8080 Static TCP HTTP Server Push (Optional)
1024 - 65535 Dynamic TCP H.245 (Call Parameters)
1024 - 65535 Dynamic UDP RTP (Video Data Streams)
1024 - 65535 Dynamic UDP RTP (Audio Data Streams)
1024 - 65535 Dynamic UDP RTCP (Control Information)

If you have any further questions about ports or VoIP and what is required get it work with Firewalls or over VPN let me know and I'll do my best to help you out.

Thank you,
Frank Mirecki

 

[probe123]

Hi,
Thanks for the reply, I know that Q931 messages use TCP port 1720, but if I filter for that port, I dont see
any call control messages, I feel this signalling port
(default 1720) is negotiated with the gatekeeper, )or there may be fire wall).I doubt about the fire wall because,
I tried to connect my probe (tcp/IP analyzer ) to the
IP phone directly, but still unable to see the Q931 messages
on port 1720, I see only Information Messages that to on
a different protocol descriminator( not 0x08 used for Q931).
I appreciate your help.
Thanks.

 

[TheLaw]

Did you ever resolve this. We are also attempting to sniff a call to/from an Avaya IP phone and do not see the expected traffic. We're looking for the rtp stream

 

[probe123]

We do see RTP streem on UDP port 1720, but could not
associate to a perticular call as we could not see Q931
call control messages on the TCP 1720 port.