NetMeeting Video/Audio problem with MN-820

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Hi gurus,

Anyone any ideas how I can configure my MN-820 base station to allow
incoming video/audio stream
for NetMeeting? Interestingly, the remote user can see/hear me, but I can't
see hear them....

I've already looked at the MS Knowledge Base, and found an article
describing the ports used by NetMeeting.
So, I enabled app-triggered port replication for NetMeeting (TCP trigger
types are all TCP - according to the article,
the UDP ones are dynamically assigned) on the following:

389, 522, 1503, 1720, 1731

But still no joy.

I know its related to the MN-820 as I hooked my PC directly to the broadband
router
and video/audio worked just fine....any ideas out there?

Thanks in advance...

Karl

 

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

How did you set the ports?

On one hand, you need to set the trigger ports to open
themselves (same port on all four cases of a line), as many
lines as ports... and on another hand you need to pick a
trigger port to open a range of potential UDP ports -- the
trigger port is on the left two boxes, and the UDP range on
the right two boxes.

You can run Command Prompt and enter netstat -ano while
running NetMeeting. It shows a list of all ports and
associated processes, so you can get an idea of which UDP
ports NetMeeting opens.

>-----Original Message-----
>Hi gurus,
>
>Anyone any ideas how I can configure my MN-820 base
station to allow
>incoming video/audio stream
>for NetMeeting? Interestingly, the remote user can
see/hear me, but I can't
>see hear them....
>
>I've already looked at the MS Knowledge Base, and found an
article
>describing the ports used by NetMeeting.
>So, I enabled app-triggered port replication for
NetMeeting (TCP trigger
>types are all TCP - according to the article,
>the UDP ones are dynamically assigned) on the following:
>
>389, 522, 1503, 1720, 1731
>
>But still no joy.
>
>I know its related to the MN-820 as I hooked my PC
directly to the broadband
>router
>and video/audio worked just fine....any ideas out there?
>
>Thanks in advance...
>
>Karl
>
>
>.
>

 

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Thanks for the advice....watch this space!

Surprised no-one else has run into this one...even more surprised Microsoft
hasn't published the required port settings ....


"lilo" <anonymous@discussions.microsoft.com> wrote in message
news:2c61801c468c8$73bcfdd0$a301280a@phx.gbl...
> How did you set the ports?
>
> On one hand, you need to set the trigger ports to open
> themselves (same port on all four cases of a line), as many
> lines as ports... and on another hand you need to pick a
> trigger port to open a range of potential UDP ports -- the
> trigger port is on the left two boxes, and the UDP range on
> the right two boxes.
>
> You can run Command Prompt and enter netstat -ano while
> running NetMeeting. It shows a list of all ports and
> associated processes, so you can get an idea of which UDP
> ports NetMeeting opens.
>
> >-----Original Message-----
> >Hi gurus,
> >
> >Anyone any ideas how I can configure my MN-820 base
> station to allow
> >incoming video/audio stream
> >for NetMeeting? Interestingly, the remote user can
> see/hear me, but I can't
> >see hear them....
> >
> >I've already looked at the MS Knowledge Base, and found an
> article
> >describing the ports used by NetMeeting.
> >So, I enabled app-triggered port replication for
> NetMeeting (TCP trigger
> >types are all TCP - according to the article,
> >the UDP ones are dynamically assigned) on the following:
> >
> >389, 522, 1503, 1720, 1731
> >
> >But still no joy.
> >
> >I know its related to the MN-820 as I hooked my PC
> directly to the broadband
> >router
> >and video/audio worked just fine....any ideas out there?
> >
> >Thanks in advance...
> >
> >Karl
> >
> >
> >.
> >

 

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

So did it solve your problem?? I am having the same issue
open the ports and still no luck.

How exactly did you solve it?

Thanks

Rafa

>-----Original Message-----
>Thanks for the advice....watch this space!
>
>Surprised no-one else has run into this one...even more
surprised Microsoft
>hasn't published the required port settings ....
>
>
>"lilo" <anonymous@discussions.microsoft.com> wrote in
message
>news:2c61801c468c8$73bcfdd0$a301280a@phx.gbl...
>> How did you set the ports?
>>
>> On one hand, you need to set the trigger ports to open
>> themselves (same port on all four cases of a line), as
many
>> lines as ports... and on another hand you need to pick a
>> trigger port to open a range of potential UDP ports --
the
>> trigger port is on the left two boxes, and the UDP
range on
>> the right two boxes.
>>
>> You can run Command Prompt and enter netstat -ano while
>> running NetMeeting. It shows a list of all ports and
>> associated processes, so you can get an idea of which
UDP
>> ports NetMeeting opens.
>>
>> >-----Original Message-----
>> >Hi gurus,
>> >
>> >Anyone any ideas how I can configure my MN-820 base
>> station to allow
>> >incoming video/audio stream
>> >for NetMeeting? Interestingly, the remote user can
>> see/hear me, but I can't
>> >see hear them....
>> >
>> >I've already looked at the MS Knowledge Base, and
found an
>> article
>> >describing the ports used by NetMeeting.
>> >So, I enabled app-triggered port replication for
>> NetMeeting (TCP trigger
>> >types are all TCP - according to the article,
>> >the UDP ones are dynamically assigned) on the
following:
>> >
>> >389, 522, 1503, 1720, 1731
>> >
>> >But still no joy.
>> >
>> >I know its related to the MN-820 as I hooked my PC
>> directly to the broadband
>> >router
>> >and video/audio worked just fine....any ideas out
there?
>> >
>> >Thanks in advance...
>> >
>> >Karl
>> >
>> >
>> >.
>> >
>
>
>.
>

 

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Karl Soar wrote:
> Hi gurus,
>
> Anyone any ideas how I can configure my MN-820 base station to allow
> incoming video/audio stream
> for NetMeeting? Interestingly, the remote user can see/hear me, but
> I can't see hear them....


That is the normal symptom for H.323 audio/video. Generally the only
solution is to designate the NetMeeting computer as the dmz machine. Make
sure it is running a software firewall ( which may need configuration for
NetMeeting).

>
> I've already looked at the MS Knowledge Base, and found an article
> describing the ports used by NetMeeting.
> So, I enabled app-triggered port replication for NetMeeting (TCP
> trigger types are all TCP - according to the article,
> the UDP ones are dynamically assigned) on the following:
>
> 389, 522, 1503, 1720, 1731

Actually 1503 and 1720 are the only tcp ports that matter incoming. but udp
ports 1024-65535 could be allocated dynamically for audio/video
transmission.



>
> But still no joy.
>
> I know its related to the MN-820 as I hooked my PC directly to the
> broadband router
> and video/audio worked just fine....any ideas out there?
>


The dmz solution is generally the easiest. It is theoretically possible to
use application triggered port forwarding but the complications are often
insurmountable.


--
Brian Sullivan
Meeting by Wire ( http://www.meetingbywire.com)
------------
Is your PC protected? --
http://www.microsoft.com/security/protect/default.asp

 

[Guest]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Sorry for the dealy in getting back to you.

Unfortunately, it didn't...just can't seem to get the hard facts on how to
enable triggering for port forwarding the
dynamic UDP ports. In the end, I switched to Windows Messenger (the person
I comunicate with fortunately
uses XP too... and this works just fine via the MN700...

Very annoying.

Karl


"Rafa Ballesteros" <rafael_ballesteros_bono@microsoft.com> wrote in message
news:2fa1a01c46d10$7acbd6e0$a301280a@phx.gbl...
> So did it solve your problem?? I am having the same issue
> open the ports and still no luck.
>
> How exactly did you solve it?
>
> Thanks
>
> Rafa
>
> >-----Original Message-----
> >Thanks for the advice....watch this space!
> >
> >Surprised no-one else has run into this one...even more
> surprised Microsoft
> >hasn't published the required port settings ....
> >
> >

 

[joker]

Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Put the computer in the DMZ to use that old piece of software.

Karl Soar wrote:
> Sorry for the dealy in getting back to you.
>
> Unfortunately, it didn't...just can't seem to get the hard facts on how to
> enable triggering for port forwarding the
> dynamic UDP ports. In the end, I switched to Windows Messenger (the person
> I comunicate with fortunately
> uses XP too... and this works just fine via the MN700...
>
> Very annoying.
>
> Karl
>
>
> "Rafa Ballesteros" <rafael_ballesteros_bono@microsoft.com> wrote in message
> news:2fa1a01c46d10$7acbd6e0$a301280a@phx.gbl...
>
>>So did it solve your problem?? I am having the same issue
>>open the ports and still no luck.
>>
>>How exactly did you solve it?
>>
>>Thanks
>>
>>Rafa
>>
>>
>>>-----Original Message-----
>>>Thanks for the advice....watch this space!
>>>
>>>Surprised no-one else has run into this one...even more
>>
>>surprised Microsoft
>>
>>>hasn't published the required port settings ....
>>>
>>>
>
>
>