Troubleshooting FAQ
From VoiceRDWiki
Troubleshooting VoiceRD Installation FAQ
This FAQ assumes your testing your installed and configured VoiceRD. Most of the errors mentioned are seen from viewing asterisk console in verbose mode.
More information on how to configure and setup your system is available in the HOWTOs section.
Contents |
Voicemail
Operator
Problem: Pressing 0 when in Voicemail does not do anything.
Solution: This should redirect to operator or whatever is set in macro-vm assuming that the operator=yes variable is set in voicemail.conf
voicerd*CLI> dialplan show macro-vm
'o' => 1. Background(one-moment-please) [pbx_config]
2. GotoIf($["foo${FROM_DID}" = "foo"]?from-pstn|s|1:from-pstn|${FROM_DID}|1) [pbx_config]
The FROM_DID variable is set in the ext-did context as a channel variable. Modify the second priority of the 'o' extension by adding an object to ou=custom,ou=extensionsConf,ou=Conf,o=voicerd and make sure that the oxyPBXConfigVariableMetric is lower than the corresponding object in ou=static,ou=extensionsConf,ou=Conf,o=voicerd.
For example you could set it to something like:
'o' => 1. Background(one-moment-please) [pbx_config]
2. Goto(aa_MyMenu|s|1) [pbx_config]
to have it go to the auto attendant menu named MyMenu.
Message Waiting Indicator(MWI)
Problem: Message Waiting Indicator(MWI) does not work.
Solution: Make sure that the mailbox is set properly on the SIP device/line. You can check this in the CLI by running the "sip show peer <somepeernumber>"
voicerd*CLI> sip show peer 1234 voicerd*CLI>
* Name : 1234 Realtime peer: No Secret : <Set> MD5Secret : <Not set> Context : from-internal Subscr.Cont. : <Not set> Language : AMA flags : Unknown Transfer mode: open CallingPres : Presentation Allowed, Not Screened Callgroup : Pickupgroup : Mailbox : 1234@default VM Extension : asterisk LastMsgsSent : 0/0 Call limit : 0 Dynamic : Yes Callerid : "" <1234> MaxCallBR : 384 kbps Expire : 40 Insecure : no Nat : Always ACL : No T38 pt UDPTL : No CanReinvite : No PromiscRedir : No User=Phone : No Video Support: Yes Trust RPID : Yes Send RPID : Yes Subscriptions: Yes Overlap dial : Yes DTMFmode : inband LastMsg : 0 ToHost : Addr->IP : 192.168.1.10 Port 5060 Defaddr->IP : 0.0.0.0 Port 5060 Def. Username: 1234 SIP Options : (none) Codecs : 0x3f1fff (g723|gsm|ulaw|alaw|g726|adpcm|slin|lpc10|g729|speex|ilbc|g726aal2|g722|jpeg|png|h261|h263|h263p|h264) Codec Order : (none) Auto-Framing: No Status : OK (4 ms) Useragent : VoiceRD/1.01 (Novacoast Inc.) Reg. Contact : sip:1234@192.168.1.10:5060
The mailbox is set to 1234@default in this example. That will notify this device/line if there are any new messages in that mailbox.
MeetMe conference rooms
All rooms Invalid
Problem: Conference rooms are all invalid.
Solution: MeetMe conferences require either a valid configured Zaptel card. If you don't have one, load the 'ztdummy' module.
Some rooms Invalid
Problem: Specific conference rooms are invalid.
Solution: Make sure you do not include the "8" prefix in the conference room number when you create it.
Problem: There is no beep when users log into my conference room.
Solution: Make sure the admin pin is not set to the same as the user pin in asterisk. You will not be notified when an admin logs in.
Creating a SIP trunk
Problem: The SIP provider requires that I set attributes that are not available under the Trunk configuration page in the web interface. Solution: The creation of a SIP trunk will create two devices that appear as objects in LDAP. Install an LDAP browser(e.g., ConsoleOne from Novell) and add the attribute you need to the appropriate device. In ConsoleOne you will need to authenticate by entering the following credentials:
Login name: vrdadmin Password: <your VoiceRD password> Tree: <the IP address of your server that is running LDAP> Context: o=voicerd
- Browse to: ou=SIPAccount,o=voicerd and locate the SIP device you would like to modify.
- Right-click the device and select Properties.
- Select the Other Tab.
- Make sure Attributes: is highlighted and click Add...
The mapping between the LDAP attributes and the attributes asterisk expects can be found in the /etc/asterisk/res_ldap.conf file under the sip section.
- Add the attribute you need(e.g., oxyPBXAccountFromUser) and type in the appropriate value.
