fax h323 gateway didn't work until fax protocol pass-through

This is an example of a dial-peer I made to make faxes work on a FAx server at a Main site. Until this command was added the faxes would time out.


dial-peer voice 606 voip
description Match Nashville numbers for FacSys
destination-pattern 04[4-9][02468]
session target ipv4:10.1.0.1
dtmf-relay h245-alphanumeric
codec g711ulaw
fax rate disable
fax protocol pass-through g711ulaw
no vad

command to have caller-id name for incoming calls

I had a H323 gateway and cisoco Callmanager. The caller-id name wasn't working on incoming calls until I added this command on the serial interface for the PRI "isdn supp-service name calling".

Example:
interface Serial0/0/1:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn supp-service name calling
no cdp enable

ASA commands that help

ASA#more system:running-config , this command shows you the running config including pre-share key

ASA#show vpn-sessiondb l2l , looks for Bytes TX and Bytes RX. Helps with vpn troubleshooting because you can tell if there is no TX Bytes.

ASA# show conn all | grep 10.0.0.1 (ip your're looking for traffic on) , you will see UIOB if traffic is going through properly.

Pix515#write net 192.168.0.10: pixconfig_tftp , the get tftpd.exe running on server and then use this command

Fwd voicemail to public folder in Unity

I had this problem were when fwd messages to a public folder I was getting NDRs in the message tracking so the voicemails were not making it to public folder. The reason for this was under the public folder permissions weren't set correctly.

- Make sure Default and Anonymous roles are set to Contributor.

- I originally had them set to none and that it was message weren't fwd to the public folder.

Configure least cost routing on Callmanager server from site A to B

- Configure route patterns on Callmanager.
## For Nashville to Knoxville calls##
route pattern: 91865.[2-9]XXXXXX
partition: Nash_local_pt <-- (local pt where phones are calling from)
gateway: Knoxville2811
discard: predot


###For Knoxville to Nashville calls###
route pattern: 91615.[2-9]XXXXXX
partition: Knox_local_pt
gateway: Nashville2811
discard: predot

In case the Nashville PRI provider requires 10 digits on all calls you would change the Nash to Knox route pattern to 91.865[2-9]XXXXXX. Remember that we are discarding predot so you would have to move the dot before the 865.

Changing a LWAP to Autonomous AP

Follow these steps to revert from lightweight mode to autonomous mode by loading a Cisco IOS release using a TFTP server:

Step 1 The PC on which your TFTP server software runs must be configured with a static IP address in the range of 10.0.0.2 to 10.0.0.30.

Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point in the TFTP server folder and that the TFTP server is activated.

Step 3 Rename the access point image file in the TFTP server folder to the default image name - it will be c1200-k9w7-tar.default for an 1200 series AP and c1130-k9w7-tar.default for an 1130 series AP

Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.

Step 5 Disconnect power from the access point.

Step 6 Press and hold the MODE button while you reconnect power to the access point.

Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button.

For the 1130 APs, hold the button until the console indicates that the button is pressed (the R LED will be solid red):

button is pressed, wait for button to be released...
button pressed for 25 seconds
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery:
image recoveryimage_recovery: Download default IOS tar image tftp://255.255.255.255/c1130-k9w7-tar.default
Once it starts uploading, the E & R LEDs will both be blinking (1130 AP). Once you release the button, you should see the console extracting files from the tarball on the TFTP server.

Step 8 Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green. You can also observe the console to see when it reboots - this is a better bet, as some APs behave differently than others in terms of LED operation.

Step 9 After the access point reboots, reconfigure the access point using the GUI or the CLI.

upgrading cisco 1130 ap with archive command

Use this command on the access point after you setup tftpd on your pc or laptop.

archive download-sw /overwrite /reload tftp://192.168.1.33/c1130-k9w7-tar.124-21a.JY.tar

- 192.168.1.33 is your pc/laptop ip address.
- c1130-k9w7-tar.124-21a.JY.tar is the firmware load that you what to upgrade to.
- After firmware is loaded it will auto delete the old firmware on access point.