Page 373 - Asterisk™: The Future of Telephony

By default, register requests will be sent via port 4569. You can direct them to a dif-
ferent port by explicitly specifying it, as follows:
register => username:password@remote-host:1234

IAX Channel Definitions

With the general settings defined, we can now define our channels. Defining a guest
channel is recommended whenever you want to accept anonymous IAX calls. This is
a very common way for folks in the Asterisk community to contact one another. Before
you decide that this is not for you, keep in mind that anyone whom you want to be able
to connect to you via IAX (without you specifically configuring an account for them)
will need to connect as a guest. This account, in effect, becomes your “IAX phone
number.” Your guest channel definition should look something like this:

[guest]
type=user
context=incoming
callerid="Incoming IAX Guest"

No doubt the spammers will find a way to harass these addresses, but
in the short term this has not proven to be a problem. In the long term,
we’ll probably use DUNDi (see Chapter 14 for more information).

If you wish to accept calls from the Free World Dialup network, Asterisk comes with
a predefined security key that ensures that anonymous connections cannot spoof an
incoming Free World Dialup call. You’ll want to set up an iaxfwd channel:

[iaxfwd]
type=user
context=incoming
auth=rsa
inkeys=freeworlddialup
If you have resources advertised on a DUNDi network, the associated user must be
defined in iax.conf:
[dundi]
type=user
dbsecret=dundi/secret
context=dundi-incoming
If you have IAX-based devices (such as an IAXy), or IAX-based users at a remote node,
you may want to provide them with their own user definition with which to connect
to the system.
Let’s say you have a user on a remote node for whom you want to define an IAX user.
We’ll call this hypothetical user sushi. The user definition might look something like
this:

IAX | 345