Fast Busy Tone on Cisco 7962

[mihailovicm]

Hi ,

when i´m dialing with the DNA / Phones the call is routed ( result is ok.)

but when i´m dialing on the device ( the same phone es in  DNA) i get fast busy ????

[Suresh Subramanian]

what is your CUCM version?

what is your Gateway Type? MGCP/H323/SIP?

in the route pattern have you assigned Route List or the gateway?

internal calls work from that phone? is it for one phone or multiple phones? is it only for 7962 model?

[mihailovicm]

what is your CUCM version?  ----  7.1.5

what is your Gateway Type? MGCP/H323/SIP?----- SIP Trunk

in the route pattern have you assigned Route List or the gateway?-----Route List

internal calls work from that phone?------   YES

is it for one phone or multiple phones? all internal phones

is it only for 7962 model?  regardless of model

----------please see the attachment. Thanks.

[afsal abdul gafoor]

Hello

Use RTMT to send the trace result, and also the send the sip trunk configuration screen shot.

Regards

Afsal Abdul Gafoor

[Suresh Subramanian]

seems the call is going out to SME (SIP.to.CUCMSME.pub).

does the call go to a phone in other cluster or is it call to external PSTN number?

can you give us the complete call flow?

if it is going to other cluster, then we need to collect the trace from both the clusters.

if the other cluster is 8.X version, you can login into RTMT of that 8.x cluster and check the session trace entering calling & called numbers. it will give you the termination cause code.

however the detailed trace from the cluster will give us more information on why the calls are failing

[mihailovicm]

seems the call is going out to SME (SIP.to.CUCMSME.pub). -----------yes

does the call go to a phone in other cluster or is it call to external PSTN number?------

I can not verify that call ever comes to sme ( at the moment the Trace is not possible ). Following the SME call goes over WAN for a SIP Fax server.

can you give us the complete call flow?

if it is going to other cluster, then we need to collect the trace from both the clusters.

if the other cluster is 8.X version, you can login into RTMT of that 8.x cluster and check the session trace entering calling & called numbers. it will give you the termination cause code.

however the detailed trace from the cluster will give us more information on why the calls are failing

[mihailovicm]

I do not know if you can start with this log

[Anas Abueideh]

Hi,

your question is not clear. please clarify your problem, with cucm version.

Anas

[Jaime Valencia]

DNA is only a simulation of routing, and it's based on the DB info.

CUCM actual routing is based on what it's loaded on memory, so they could be out of sync, simply reboot to rule that out, or it can be that you're not sending what your telco expects via your SIP trunk, run debugs/traces to confirm that.

[mihailovicm]

I can not verify that call ever comes to sme ( at the moment the Trace is not possible ).

[mihailovicm]

I do not know if you can start with this log.

Calling Number: 49893330857

[afsal abdul gafoor]

It seems some firewall will be coming in to the network and also need to check the nating.

If so pls give more clues.

Regards

Afsal Abdul Gafoor