24.11.2014 Views

General Information

General Information

General Information

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

marked as dynamic and can not be removed or changed. If there already was an voip entry with the<br />

same IP address, it is marked as registred. Remote-address can not be changed for these entries too,<br />

but registered voip voice ports can be removed - they will stay as dynamic ones. If there already is a<br />

dynamic voip voice port and a static one with the same IP address is added, then instead of dynamic<br />

entry, registered will appear.<br />

Dynamic entries disappear when corresponding endpoint unregisters itself from the gatekeeper.<br />

Registered entries are static and will stay even after that endpoint will be unregistered from this<br />

gatekeeper.<br />

Registered telephone numbers are added to /ip telephony numbers table. Here is exactly the same<br />

idea behind dynamic and registered telephone numbers as it is with voip voice ports.<br />

When an endpoint registers to the gatekeeper, it sends its own telephone numbers (aliases and<br />

prefixes) within this registration request. /ip telephony numbers entry is registered to the endpoint<br />

only if voice-port for that entry is local (not voip). If dst-pattern contains '.' or '_', it is sent as<br />

prefix, otherwise - as alias. The known part of the dst-pattern is sent as prefix. If there is no known<br />

part (dst-pattern is "_" or "...", for example), then this entry is not sent at all.<br />

Property Description<br />

gatekeeper (none | local | remote; default: none) - Gatekeeper type to use<br />

• none - don't use any gatekeeper at all<br />

• local - start and use local gatekeeper<br />

• remote - use some other gatekeeper<br />

remote-address (IP address; default: 0.0.0.0) - IP address of remote gatekeeper to use. If set to<br />

0.0.0.0, broadcast gatekeeper discovery is used<br />

remote-id (name) - name of remote gatekeeper to use. If left empty, first available gatekeeper will<br />

be used. Name of locally started gatekeeper is the same as system identity<br />

registered (read-only: yes | no) - shows whether local H.323 endpoint is registered to any<br />

gatekeeper<br />

registered-with (read-only: name) - name of gatekeeper to which local H.323 endpoint is<br />

registered<br />

Example<br />

In most simple case with one phonejack card and some remote gatekeeper, configuration can be as<br />

follows:<br />

[admin@MikroTik] ip telephony voice-port> print<br />

Flags: X - disabled<br />

# NAME TYPE AUTODIAL<br />

0 phonejack1 phonejack<br />

1 voip1 voip<br />

[admin@MikroTik] ip telephony voice-port voip> print<br />

Flags: X - disabled, D - dynamic, R - registered<br />

# NAME AUTODIAL REMOTE-ADDRESS JITTER-BUFFER PREFERED-CODEC SIL FAS<br />

0 voip1 0.0.0.0 0s none no yes<br />

[admin@MikroTik] ip telephony numbers> print<br />

Flags: I - invalid, X - disabled, D - dynamic, R - registered<br />

# DST-PATTERN VOICE-PORT PREFIX<br />

Page 370 of 568<br />

Copyright 1999-2005, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.<br />

Other trademarks and registred trademarks mentioned herein are properties of their respective owners.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!