Switching to VoIP

This is the Title of the Book, eMatter Edition

Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.

306

|

Chapter 13: Network Infrastructure for VoIP

Route incoming IAXTel calls

At this point, we’ve got IAXTel calls coming to the from-iaxtel context, but this con-

text doesn’t exist yet in the dial-plan. So, in extensions.conf, we can use this context

to tell Asterisk what to do with the calls. In this case, we’ll just have them ring a Zap-

tel channel and then dump to voice mail box 100 if there’s no answer after 45

seconds:

[from-iaxtel]

exten => s,1,Dial(Zap/1,45)

exten => s,2,Voicemail(100)

Monitoring registrations

When you set up VoIP trunks from the Asterisk server to various providers, what

you’re really doing is registering Asterisk as a VoIP client. To monitor the status of

each trunk’s registration, use the

sip show registry and iax2 show registry com-

mands. Here’s a SIP trunk registration in progress:

pbx*CLI> sip show registry

Host Username Refresh State

access1.voicepulse.com:5060 s00227788 120 Auth. Sent

Here’s an IAX trunk registration:

pbx*CLI> iax2 show registry

Host Username Perceived Refresh State

69.73.19.178:4569 tedwalling <Registered> 60 Registered

You can also follow VoIP trunk registrations in Asterisk’s detail log output.

WAN Design

The layout of your WAN has huge implications for VoIP, particularly when it comes

to failover ability, disaster preparedness, and latency. ...