Re: TAPI ports
From: Matthias Moetje (moetje_at_terasens_nospam_.de)
Date: 02/23/05
- Next message: Fabricio: "RE: Error routing SAPI SR and TTS streams through modem using TAPI 3 a"
- Previous message: Matthias Moetje: "Re: restarting telephony service from code"
- In reply to: Carlo: "Re: TAPI ports"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 20:24:59 +0100
Carlo,
for H.323 it is not sufficient to open a number of ports
on your firewall. H.323 dynamically assigns ports, therefore
you need a firewall that explicitly supports H.323 or comes
with a gatekeeper service.
Best regards,
Matthias Moetje
-------------------------------------
TERASENS GmbH
Ackermannstraße 3
80797 München
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot de
www: www.terasens.de
-------------------------------------
"Carlo" <c.ieva@tiscali.it> wrote in message
news:OPtRfxcGFHA.2736@TK2MSFTNGP12.phx.gbl...
> The architecture is based upon H323.TSP
>
> Thanks
>
> "Andreas Marschall [MVP TAPI]" <Andreas.Marschall@I-B-A-M.de> ha scritto
nel
> messaggio news:e6vv5UcGFHA.3068@tk2msftngp13.phx.gbl...
> > "Carlo" <c.ieva@tiscali.it> schrieb im Newsbeitrag
> > news:%23eO4hEcGFHA.904@tk2msftngp13.phx.gbl...
> > > Where I can find the list of TCP/UDP ports needed from TAPI? I've been
> > > experienced some firewall problems.
> >
> > Carlo,
> > what exactly are you refering to?
> >
> > A specific TSP (e.g. H323.TSP) or TAPI client / server architecture (via
> > RemoteSP.TSP)?
> >
> > The latter is using RPC.
> > You can check with NETSTAT:
> > Right after a client's attempt to connect (lineIntialize)
> > run netstat in a command window.
> > Look for two sockets like the following on the client:
> >
> > Proto Local Foreign State
> > TCP CLIENT:xxxx SERVER:nbsession ESTABLISHED
> > TCP CLIENT:251 SERVER:yyyy ESTABLISHED
> >
> >
> > And on the server:
> >
> >
> > Proto Local Foreign State
> > TCP SERVER:nbsession CLIENT:xxxx ESTABLISHED
> > TCP SERVER:yyyy CLIENT:251 ESTABLISHED
> >
> >
> > If you don't see the first connection, or it's not in the
> > established state, this means the client can't connect to the
> > server's net bios port (over which the RPC takes place).
> > Make sure the user has "Access this computer from network"
> > rights on the server.
> >
> >
> > The same goes for the second connection. Make sure the account
> > that TAPISRV runs under on the server has "Access this computer
> > from network" rights.
> >
> >
> >
> > See my TAPI and TSPI FAQ:
> > Q: What is the Microsoft® TAPI client / server architecture ?
> >
>
http://www.i-b-a-m.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm#_Q:_What_is_
> 10
> >
> > --
> > Best Regards
> > Andreas Marschall
> > Microsoft MVP for TAPI / Windows SDK
> > TAPI / TSP Developer and Tester
> > http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
> > * Please post all messages and replies to the newsgroup so all may
> > * benefit from the discussion. Private mail is usually not replied to.
> > * This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> >
>
>
- Next message: Fabricio: "RE: Error routing SAPI SR and TTS streams through modem using TAPI 3 a"
- Previous message: Matthias Moetje: "Re: restarting telephony service from code"
- In reply to: Carlo: "Re: TAPI ports"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
