Redial feature gets busy tone but call works with digit-by-digit dialing

[learner2008]

We are having an issue with local and mobile dialing in Argintia office. There is newly installed 2921 router with E1 R2 connection to PSTN.

the symptom is that when we dial local PSTN or mobile number in digit-by-digit, call goes through. When we use "Redial" feature on IP phone, we keep getting busy tone right away.

I am posting two debugs - one for a good call to a local mobile number and one is a bad call to same number.

Can anyone help me out to find out what the problem is?

Thanks!

[stepwebs]

Not sure how the good one is missing it and how the bad one is even hitting it but bad one is hitting the new toll fraud feature

004353: *Oct 19 17:50:31.885 UTC: //1337/809ECF8DA300/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 1337 with tag 441 to app "_ManagedAppProcess_TOLLFRAUD_APP"

Its being disconnected straight after so rekon this is the first thing to check.

http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a0080b3e123.shtml

Stephen

[learner2008]

Stephen,

I got "Forbidden File or Application" error while accessing the link. Is there any way you can copy the link content to my email?

Thanks,

Jessica

[Ray Watkins · Accepted solution]

Both calls are coming into the gateway from the same dial-peer and therefore from the same trusted IP source. You have the following options.

How to Return to Pre-15.1(2)T Behavior

Source IP Address Trust List

There are three ways to return to the previous behavior of voice       gateways before this trusted address toll-fraud prevention feature was       implemented. All of these configurations require that you are already running       15.1(2)T in order for you to make the configuration change.

1. Explicitly enable those source IP addresses from which you would like           to add to the trusted list for legitimate VoIP calls. Up to 100 entries can be           defined. This below configuration accepts calls from those host           203.0.113.100/32, as well as from the network 192.0.2.0/24. Call setups from           all other hosts are rejected. This is the recommended method from a voice           security perspective.

   voice service voip
    ip address trusted list
     ipv4 203.0.113.100 255.255.255.255
     ipv4 192.0.2.0 255.255.255.0

2. Configure the router to accept incoming call setups from all source           IP addresses.

   voice service voip
    ip address trusted list
     ipv4 0.0.0.0 0.0.0.0

3. Disable the toll-fraud prevention application completely.

   voice service voip
    no ip address trusted authenticate

[learner2008]

Ray,

Thanks for posting the solutions for me. This issue has been fixed by applying the 3rd option - completely disabling the toll-fraud application.

Thanks for help!

Jessica Wang