Adi Linden schrieb:
> ...
> In iax.conf eaxh peer has a context in which I can specify the context an
> inbound call will be placed in. I don't see anything like this in the
> oh323.conf file or the oh323 documentation.
Hi,
there is a workaround what is doing this job in most cases:
Use as general context in oh323.conf something like e.g.
context=oh323
Then in extensions.conf or better in a file like oh323peers.conf
included in extensions.conf switch to "contexts per peer" via gotoifs:
e.g.
[oh323]
;;;;;; below here are all peers with fixed ip addresses
exten => _.,1,gotoif,$[${OH323_RADDR} = \
1.2.3.4]?peer01|BYEXTENSION|1
; below only traffic from our gatekeeper
exten => _.,2,gotoif,$[${OH323_RADDR} != \
5.6.7.8]?4
;;;;;; below here are all peers which prefer authenticating
; by H.323 username and passoword via our gatekeeper
exten => _.,3,gotoif,$[${CALLERIDNAME} = \
peer02]?peer02|BYEXTENSION|1
;;;;;;; everyone who arrived here is not authorized
exten => _.,4,noOp(no such peer)
exten => _.,5,hangup
Wheras 1.2.3.4 is the fixed remote ip address from
your peer1.
5.6.7.8 is the ip address from your gatekeeper (e.g. gnugk)
which verifies the H.323 usernames via passwords.
You can expand this example with further fixed ip address
and further users, which authenticate via your gatekeeper.
Roger.
--
Dr. Roger Schreiter
PLANinterNET GmbH
Gesch?ftsf?hrer
Hauptstrasse 6
D-74391 Erligheim
Tel.: +49 7143 408091-5
oder: +49 7143 87205-6 (Vermittlung)
Fax: +49 7143 87205-7
Email: schreiter@planinternet.de
WWW: http://www.planinternet.de