Assuming that configuration instructions in Configuring Blueworx Voice Response Voice over IP have been followed, it should
be possible to enable Blueworx Voice Response channels
and make a Voice Over IP call into Blueworx Voice Response DTNA.
If you have problems in doing this, the following checks may be useful:
- Ensure that you have run a dt_setowner command
with the -n option to create the DTNA devices. Use
the -t T1 or -t E1 options to set
T1 (North America and Japan) or E1 (rest of world) as appropriate.
- Use lsdev -C | egrep "vnaio|dtline" to ensure
that you have created the devices and that they are all available.
- Bring up Blueworx Voice Response and
configure VoIP using the Pack Configuration window as described in
section Configuring Blueworx Voice Response for Voice over IP.
- Save your configuration and restart Blueworx Voice Response.
- Open the Blueworx Voice Response System
Monitor window. Enable at least one trunk and bring channels into
service. (Alternatively, use the wvrtrunk command
to do this. Refer to the Blueworx Voice Response for AIX:
Managing and Monitoring the System information for details of the wvrtrunk command.)
- Make a VoIP call into the Blueworx Voice Response machine
from a ‘softphone’.
- Check for any Red or Yellow alarms in the System Monitor window.
- If the call is refused (the problem is at the SIP signalling level),
use the VOIP_MONITOR command to trace SIP
traffic flows. See Using VOIP_MONITOR.
- Check that the SIP setup sequence is following the standard INVITE,
100, 180, 200, ACK sequence.
- The most common error is 415 Media Not Supported which
is probably due to a mismatch in codecs between what is being offered
and what is supported.
Note: This includes the Telephone
Event media option (also known as RFC2833 or RTP
Payload). If this is being offered by a remote endpoint, Blueworx Voice Response must
be configured for RFC2833 (VoIP DTEA and DTNA group, DTMF
Transmission Method).
- If the call appears to be setup correctly (System Monitor shows
an active channel) and you still hear no voice, the problem is probably
either due to the application not sending any voice or some problem
with the IP connection between Blueworx Voice Response and
your softphone.
- Using standard AIX tools, check IP connectivity between the two
machines.
- If you have a NAT/Firewall between your machine and Blueworx Voice Response,
ensure that you have used the Use Symmetric RTP option
(VoIP DTEA and DTNA Media group).