IP Telephoney - PC to PC
#1
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Didcot, South Oxfordshire
Posts: 1,999
Likes: 0
Received 0 Likes
on
0 Posts
Has anybody tried www.pc-telephone.com?
It looks harmless enough and lets you talk PC to PC for free and I have mine setup through a Nat'd router via opening port 9084. It says it also works on dialup as slow as 28.8kbps...those were the days
Is there anything I should watch out for or is there something better I can get for free?
Cheers, Jon
It looks harmless enough and lets you talk PC to PC for free and I have mine setup through a Nat'd router via opening port 9084. It says it also works on dialup as slow as 28.8kbps...those were the days
Is there anything I should watch out for or is there something better I can get for free?
Cheers, Jon
#3
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Didcot, South Oxfordshire
Posts: 1,999
Likes: 0
Received 0 Likes
on
0 Posts
forgot about that....and it comes as standard with win2k
Im set up...do I need to open any ports on my NAt'd router for it to work?
Im set up...do I need to open any ports on my NAt'd router for it to work?
#4
It probably uses H.323 in teh same way as NetMeeting does.
Establishing a NetMeeting Connection with a Firewall
When you use NetMeeting to call other users over the Internet, several IP ports are required to establish the outbound connection. The following table shows the ports, their functions, and the resulting connection.
Port Function Outbound Connection
389 Internet Locator Service (ILS) TCP
522 User Location Service TCP
1503 T.120 TCP
1720 H.323 call setup TCP
1731 Audio call control TCP
Dynamic H.323 call control TCP
Dynamic H.323 streaming Real-Time Transfer Protocol (RTP) over UDP
If you use a firewall to connect to the Internet, it must be configured so that the IP ports are not blocked.
To establish outbound NetMeeting connections through a firewall, the firewall must be configured to do the following:
Pass through primary TCP connections on ports 389, 522, 1503, 1720, and 1731.
Pass through secondary TCP and UDP connections on dynamically assigned ports (1024-65535).
The H.323 call setup protocol dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol and the H.323 call setup protocol dynamically negotiate UDP ports for use by the H.323 streaming protocol, called the Real-Time Transfer Protocol (RTP). In NetMeeting, two UDP ports are determined on each side of the firewall for audio and video streaming, for a total of four ports for inbound and outbound audio and video. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically.
NetMeeting directory services require port 389. Microsoft Internet Locator Service (ILS) servers, which support the Lightweight Directory Access Protocol (LDAP) for NetMeeting, also require port 389.
I might have to get my Cisco IP phone down from the loft now that it is starting to take off.
Establishing a NetMeeting Connection with a Firewall
When you use NetMeeting to call other users over the Internet, several IP ports are required to establish the outbound connection. The following table shows the ports, their functions, and the resulting connection.
Port Function Outbound Connection
389 Internet Locator Service (ILS) TCP
522 User Location Service TCP
1503 T.120 TCP
1720 H.323 call setup TCP
1731 Audio call control TCP
Dynamic H.323 call control TCP
Dynamic H.323 streaming Real-Time Transfer Protocol (RTP) over UDP
If you use a firewall to connect to the Internet, it must be configured so that the IP ports are not blocked.
To establish outbound NetMeeting connections through a firewall, the firewall must be configured to do the following:
Pass through primary TCP connections on ports 389, 522, 1503, 1720, and 1731.
Pass through secondary TCP and UDP connections on dynamically assigned ports (1024-65535).
The H.323 call setup protocol dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol and the H.323 call setup protocol dynamically negotiate UDP ports for use by the H.323 streaming protocol, called the Real-Time Transfer Protocol (RTP). In NetMeeting, two UDP ports are determined on each side of the firewall for audio and video streaming, for a total of four ports for inbound and outbound audio and video. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically.
NetMeeting directory services require port 389. Microsoft Internet Locator Service (ILS) servers, which support the Lightweight Directory Access Protocol (LDAP) for NetMeeting, also require port 389.
I might have to get my Cisco IP phone down from the loft now that it is starting to take off.
#5
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Didcot, South Oxfordshire
Posts: 1,999
Likes: 0
Received 0 Likes
on
0 Posts
Cheers Ian - I had read that bit in the 240 page Netmeeting manual
I can setup PAT in my Zyxel routers telnet interface for teh five TCP/UDP ports no problem but what are MS eferring to by secondary bypass?
I really do not fancy opening ports 1000 - 65000
[Edited by Rusty Festa - 8/8/2003 2:17:17 AM]
I can setup PAT in my Zyxel routers telnet interface for teh five TCP/UDP ports no problem but what are MS eferring to by secondary bypass?
I really do not fancy opening ports 1000 - 65000
[Edited by Rusty Festa - 8/8/2003 2:17:17 AM]
#7
Guest
Posts: n/a
Me and my mates use either roger wilco or sidewinder game voice for voice over ip. Both are free and very good, especially for online gaming. The sidewinder software can also be bought with a piece of hardware that allows you to set channels up I think where you can have a conference for example and block certain people off and then allow them back into the conversation again. I know its not business software but very good for home use etc.
Thread
Thread Starter
Forum
Replies
Last Post