Gå til innhold
Trenger du hjelp med internett og nettverk? Still spørsmål her ×

Noen som vet hvilken port jeg trenger


Anbefalte innlegg

Videoannonse
Annonse

skal du ha det inn med teskjeer?

 

Audio and Video

 

When negotiating an audio-video session, dynamic ports were chosen for the audio-video (AV) stream. Dynamic ports are used to enable the application to work regardless of what other applications are running on the system and using port resources. In the .NET Messenger case the session invitation was sent by station B to the address it received for station A.

 

The following issues might arise if a firewall or NAT were present in these scenarios:

The address provided by A in either the session invite for session signaling, or in the session acceptance for the UDP streams, might be an internal address that is translated by a NAT device?an invalid (or fake) address for B to use to contact A. In other scenarios with the 4.5 client, A might initiate the session, but the same or similar addressing issues will exist.

When B sends the session invitation to A, this invitation is sent using the IP address and port passed from A to B. For this to work, this port must be enabled to pass through any firewall between A and B.

The actual Real-time Transport Protocol (RTP) streams are sent using dynamically allocated UDP ports in the range of 5004 - 65535. Without a way to open these UDP ports on any firewall in the path dynamically, the streams will fail to reach their destination.

 

Nå fikk du vel svar på ditt og det stod hvor jeg linket

Lenke til kommentar
skal du ha det inn med teskjeer?

 

Audio and Video

 

When negotiating an audio-video session, dynamic ports were chosen for the audio-video (AV) stream. Dynamic ports are used to enable the application to work regardless of what other applications are running on the system and using port resources. In the .NET Messenger case the session invitation was sent by station B to the address it received for station A.  

 

The following issues might arise if a firewall or NAT were present in these scenarios:  

The address provided by A in either the session invite for session signaling, or in the session acceptance for the UDP streams, might be an internal address that is translated by a NAT device?an invalid (or fake) address for B to use to contact A. In other scenarios with the 4.5 client, A might initiate the session, but the same or similar addressing issues will exist.

When B sends the session invitation to A, this invitation is sent using the IP address and port passed from A to B. For this to work, this port must be enabled to pass through any firewall between A and B.

The actual Real-time Transport Protocol (RTP) streams are sent using dynamically allocated UDP ports in the range of 5004 - 65535. Without a way to open these UDP ports on any firewall in the path dynamically, the streams will fail to reach their destination.

 

Nå fikk du vel svar på ditt og det stod hvor jeg linket

 

det går ikke ann å lage en range ¨fra 5004-65535

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
  • Hvem er aktive   0 medlemmer

    • Ingen innloggede medlemmer aktive
×
×
  • Opprett ny...