cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

1897
Views
0
Helpful
3
Replies
Highlighted

H323 endpoint dialing SIP format

Hi,

I am experiencing this kind of issue:


If endpoint-1 with public IP 122.x.x.x will dial "411@company.com" using H323 it was successful.


If endpoint-2 is behind firewall will dial "411@company.com" using H323 call will fail

On the endpoint the message says "unable to setup encrypted call, turn off encryption"


Same settings wasconfigured on endpoint-1 and endpoint-2. The only difference is the network parameters, endpoint-1 on public while endpoint-2 on private behind firewall.


I think this is a firewall issue, what should we check on the firewall for a H323 endpoint to dial the " 411@company.com" address format?


Thank you for help..


Br,


Acevirgil

Everyone's tags (2)
3 REPLIES 3
Collaborator

H323 endpoint dialing SIP format

Firstly, the address is not SIP format per see, it is H.323 Annex O URI format, but yes, SIP URIs look the same as well.

What kind of end-points are these, and which software version do they run?

What jumps out at me is this "endpoint-2 on private behind firewall" - so, NAT'ed with other words - in which case you would have to set up a public address and use a static route between the private and the public address, or register the system with a VCS-E or something similar. Remember, the private address is not routable on the internet.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.

H323 endpoint dialing SIP format

Hi Jens,

Thank you for your response.

The endpoint-2 is NAT'ed. Could you provide list of specific firewall ports needed to make it work?

Thank you for help.

Br,

Acevirgil

Collaborator

Re: H323 endpoint dialing SIP format

Well, then it either needs to register with something like a VCS-E, or the end-point you are calling needs to be behind a VCS-E/VCS-S type of set-up and your endpoint needs to be H.460.18/19 compliant.

If none of that applies, then you need to give it a public address and do that static route between the private and the public address, or if applicable use the NAT settings in the end-point.

Since you haven't said what kind of end-point this is, this gives you ports for MXPs and C-series;

https://supportforums.cisco.com/thread/2154000

There's also this doc:

https://supportforums.cisco.com/docs/DOC-18565

This Whitepaper might also be of interest;

http://www.cisco.com/en/US/docs/telepresence/endpoint/mxp-series/white_papers/tandberg_h323.pdf

/jens

Please rate replies and mark question(s) as "answered" if applicable.

Please rate replies and mark question(s) as "answered" if applicable.
CreatePlease to create content
Content for Community-Ad
FusionCharts will render here