cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2838
Views
55
Helpful
24
Replies

Unable to Dial Long Distance numbers fromCIPC(SCCP) Deskphone(SIP)work

chaitusite
Level 1
Level 1

Unable to dial some numbers from CIPC (SCCP) phone, but Desk Phone(SIP) calls are working with Same CSS and Device pool.

CUCM Version:11.5.1.13901-3,

 

call flow:

CIPC(SCCP)--->CUCM--->Gateway(H.323)--->PSTN(PRI)--->Notworking

 

Desk Phone(SIP)--->CUCM--->Gateway(H.323)--->PSTN(PRI)--->Working

 

 

Thanks,

Krishna

1 Accepted Solution

Accepted Solutions

Based on your complete shared configuration I would suggest that you make these changes.

!
voice service voip
 no allow-connections h323 to h323
 no allow-connections h323 to sip
 no allow-connections sip to h323
 no allow-connections sip to sip
!
voice translation-rule 1
 rule 1 /^9\(.*\)/ /\1/
!
voice translation-profile PSTN-OUT
 translate called 1
!
voice-port 0/1/0:1
 translation-profile outgoing PSTN-OUT
!
dial-peer voice 1 pots
 description ### Incoming from PSTN ###
 tone ringback alert-no-PI
 call-block translation-profile incoming REJECT-CALLS
 tone ringback alert-no-PI
 incoming called-number .
 direct-inward-dial
!
dial-peer voice 10 pots
 description ### Outgoing to PSTN ###
 tone ringback alert-no-PI
 destination-pattern 9T
 progress_ind setup enable 3
 progress_ind alert enable 8
 progress_ind progress enable 8
 progress_ind connect enable 8
 progress_ind disconnect enable 8 
 port 0/1/0:1
 huntstop
 forward-digits all
!
dial-peer voice 20 voip
 description ### Outgoing to CUCMPub ###
 preference 2
 destination-pattern [346]...$
 session target ipv4:10.6.X.X
 voice-class codec 1
 dtmf-relay h245-alphanumeric h245-signal cisco-rtp
 huntstop
 no vad
!
dial-peer voice 21 voip
 description ### Outgoing to CUCMSub ###
 preference 1
 destination-pattern [346]...$
 session target ipv4:10.6.X.X
 voice-class codec 1
 dtmf-relay h245-alphanumeric h245-signal cisco-rtp
 no vad
!
dial-peer voice 11 voip
description ### Incoming from CUCM ###
incoming called-number .
voice-class codec 1
dtmf-relay h245-alphanumeric h245-signal cisco-rtp
no vad
! no dial-peer voice 22 voip no dial-peer voice 23 voip no dial-peer voice 24 voip no dial-peer voice 25 voip


Response Signature


View solution in original post

24 Replies 24

b.winter
VIP
VIP

What have you already troubleshooted?

Have you compared a working call with a non-working call?

 

You cannot just scream for help, without doing first steps of troubleshooting on your own.

 

Also, without any logs, nobody can help either.

 

Is the non-working call hitting the GW? If not, then probably the problem is on CUCM side.

If it is hitting the GW, than compare a working and a non-working call. See, if it number formats are the same, the calls using the same dial-peers, ...

chaitusite
Level 1
Level 1

I am getting the error on CIPC "High Traffic Try again Later"

chaitusite
Level 1
Level 1

both the phones are having same configuration CSS, Device Pool but still CIPC all is not working , checked DNA looks fine

Again:

What have you already troubleshooted?

Have you compared the logs of a working call with a non-working call? (RTMT logs, GW logs, ...)

 

And also: if you would have searched the internet for "High Traffic Try again Later", you would have find tons of old cisco community threads regarding this error. Maybe one of those could have helped, before opening another post.

 

The forum is not here for you to sit back and let others do your job.

chaitusite
Level 1
Level 1

i have checked the previous posts and that did not helped me and it is not having the proper solution for my issue , i know what i have done, i am not lazy guy like you simply doing post with out giving proper suggestion, i am not asking you to solve my issue, if you have knowledge you should have helped , i know you know nothing snow. 

Please post the output from from debug voip ccapi inout and debug isdn q931 from you gateway for both a working and non working call.



Response Signature


Hi Roger,

Since it is a remote site, now i have made only test call from CIPC and attaching the GW Debug, i will post Working one once i had some one at site.

You could try to remote control a phone at the site with this crafty little tool that the one and only @Anthony Holloway so kindly has made available.

https://addons.mozilla.org/en-US/firefox/addon/cisco-phone-controller/



Response Signature


Kindly share the debug isdn q931 outputs while testing a non working calls. That also help us.



Response Signature


Nobody can give you anything, without you delivering the information.

By just describing symptoms and not delivering any logs / configs, nobody can't do anything and won't give any suggestions.

Nobody can read anybody's mind...

That's why I asked for logs...

 

Like @Roger Kallberg said, please also include debug isdn q931 in your logs.

As far as I see it:

Router tries to route the call via dial-peer 23 --> but gets Cause Code 1 back (unallocated / unassigned number)

Router tries again to route the call via dial-peer 22 --> but gets again Cause Code 1 back (unallocated / unassigned number)

  • Maybe you sending it down the wrong dial-peer, or sending the numbers in wrong format, ...

Router tries again to route the call via dial-peer 10 --> gets Cause Code 16 back (normal call clearing)

 

Could you please also post the config of the router? (strip of any usernames / passwords)

Scott Leport
Level 7
Level 7

Hi, 

 

Difficult to say for sure without any logs provided of your failed call. 
If DNA is fine, the next stage is to focus your troubleshooting on the gateway I would say. 
Also as @b.winter said, there are a few hits on the error message "High Traffic try again later" and they more or less match the issue you describe. 

i have collected debugs from the gateway for working and non working calls,

 

called number :408052
calling number:444435XXXX

Asper the debugs,

 

Calling Number=408052

Called Number=4444353199

 

can you share the config for.

Outgoing Dial-peer=23

Outgoing Dial-peer=22

Outgoing Dial-peer=10



Response Signature