IOS Toll Fraud Prevention

I was recently configuring a VG202 (yeah that little cutie) for a customer and when making inbound test calls they were failing:-

I checked the configuration and there was no reason for the call to fail, did a debug voip ccapi inout and saw the following error:-

>>>>CCAPI handed cid 19 with tag 2000 to app “_ManagedAppProcess_TOLLFRAUD_AP
*Mar  9 02:41:02.915: //19/0050FCDF0800/CCAPI/ccCallDisconnect:
Cause Value=21, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect C
ause=0)

Hmm.. i thought this was only applicable to IOS 15.X and above but seems like i was wrong, looks like this 12.4(20r)YA1 has Toll Fraud mechanism

The following command <voice iec syslog>will also help you get toll fraud debugs;

*Mar  9 02:36:17.163: %VOICE_IEC-3-GW: Application Framework Core: Internal Erro
r (Toll fraud call rejected): IEC=1.1.228.3.31.0 on callID 13
*Mar  9 02:36:17.283: %VOICE_IEC-3-GW: Application Framework Core: Internal Erro
r (Toll fraud call rejected): IEC=1.1.228.3.31.0 on callID 14

you can either create a trusted ip access or disable it totally; see Toll-Fraud Prevention Feature in IOS Release 15.1(2)T for more information

Advertisements

ISDN Disconnect “Cause i = 0x829F”

Caller is able to recieve calls but unable to make calls, when making a call they get a  flat dial tone.

Traces show the following:

Dec 20 10:51:51.676: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x
95B8
Cause i = 0x829F – Normal, unspecified

The Cause code 82 is related to the receiving equipment (telco switch) requesting to use a channel that is not activated on the interface for calls.

This looks like an issue with BT who have deactivated the line (in this case, due to not paying bills)

Continue reading

Quick IOS upgrade

Following is a quick listing of the commands you need to use when upgrading the IOS firmware on legacy Cisco routers (series 1600, 2000, 2500, 3000, AS5100 and AS5200). You should consult the Cisco web site to upgrade newer models. The process involves two phases: one, set the flash to read-write and reboot; two, download the firmware and reboot.

You must setup a TFTP server and make the IOS binary file available for download. If your router is not on the same network segment as your TFTP server, be sure both devices have a default route configured so that they may access one another. I recommend using a Linux box for your TFTP server, and limit access to the service with both ipchains/iptables and the tcp-wrappers hosts.allow file.

The following sequence of commands can be entered via the console port, or by telnet session. I recommend you have access to the console port if something fails . . . you’ve been warned!

enable
conf t
config-register 0x2101
^Z
wr mem
reload

The router will reboot and the flash will now be in read-write mode. This is called “boot mode.” Avoid saving anything in this mode and answer no to any prompts about saving your current configuration. If you do save your config while in this mode, it may be partially or completely erased…

enable
conf t
config-register 0x2102
^Z
copy tftp flash

it’ll prompt for ip address…
it’ll prompt for filename…
use same name to save as…
when asked about erase say YES to confirm…

reload
answer NO to save current config
answer YES to continue with reload

If you pray really hard, and offer up the right sacrifices, at this point you’ll be looking at a successful router upgrade!

If connecting via the console port, make sure your terminal settings are as follows:

VT100
9600 bps
8 data bits
1 stop bit
no parity
no flow control

http://www.cisco.com/warp/public/130/sw_upgrade_proc_ram.shtml