Solved: Ok, Thanks, So side B is

Kaushik Ray · ‎06-15-2015

Hello I have a setup where the two ends of link are routers conencted to PABX

Trunk dialling is required but when then call there is a message "Call Cannot be completed" before the call is actually forwarded and established fine.

Any advise as to how this can be overcome? Let me know if any other relevant information is needed.

the configuration on the E1s are as follows:

A end

!
controller E1 0/0/1
framing NO-CRC4
pri-group timeslots 1-31
description ### PABX MITEL ###
!

!
interface Serial0/0/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving T302 2000
isdn incoming-voice voice
isdn send-alerting
isdn bchan-number-order ascending
no cdp enable

!
voice-port 0/0/1:15
cptone GB
timeouts interdigit 5
bearer-cap Speech
!

B end

!
controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31
description ### PABX MITEL ###
!

!
voice-port 0/0/0:15
cptone GB
timeouts interdigit 5
bearer-cap Speech
!

!
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn overlap-receiving T302 2000
isdn incoming-voice voice
isdn send-alerting
isdn bchan-number-order ascending
no cdp enable
!

Amit Kumar · ‎06-16-2015

Hello Kaushik,

I have gone through debug output, and problem is due to some misconfiguration in dial-peers.

So call is routed in two attempts.

- First gateway routes the call using first digit, so there has been no dial-peers for that, so that's why you get that announcement first.

Incoming Dial-peer=4000

Called Number=8(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=1001, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)

Failure observed:

*Jun 15 14:39:49.791: //179/2CFC01BE8037/CCAPI/cc_api_call_disconnected:
   Cause Value=1, Interface=0x271EB1C, Call Id=179

- After failure to route call with one dial-peer, as per default hunting mechanism it tries to send the call again , with another dial-peer.

Called Number=8268(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3001, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
*Jun 15 14:39:49.803: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

This time call connects. So problem seems to be happened due to these two dial-peers.

dial-peer voice 1000 voip
 translation-profile outgoing profile1
 preference 2
 destination-pattern .
 progress_ind setup enable 3
 session target ipv4:
 dtmf-relay h245-alphanumeric
 playout-delay nominal 130
 playout-delay mode fixed
 fax-relay ecm disable
 fax rate 9600
 fax nsf 000000
 ip qos dscp cs5 media
 ip qos dscp cs5 signaling
 clid network-number 441224374190
 no vad
!
dial-peer voice 1001 voip
 translation-profile outgoing profile1
 preference 1
 destination-pattern .
 progress_ind setup enable 3
 session target ipv4:
 dtmf-relay h245-alphanumeric
 playout-delay nominal 130
 playout-delay mode fixed
 fax-relay ecm disable
 fax rate 9600
 fax nsf 000000
 ip qos dscp cs5 media
 ip qos dscp cs5 signaling
 clid network-number 441224374190
 no vad
!

As they can route the call using only one digits, which is for sure , will be rejected by other end, so you get that announcement.

So to fix this problem, either you can shut these dial-peer if they are not in use, or you can modify the destination-patter, so that it will not match with any random digit.

so destination pattern should look like this:

destination-pattern .T or destination-pattern ....T

Also direct-inward-dial command is not intended for outgoing dial-peers , so you can remove it from POTS dial-peer which are for outgoing.

Thanks,

Amit

View solution in original post

Kaushik Ray · ‎06-15-2015

just did a debug and the router accepts the digits separately despite the overlap command; the same thing is working fine from the other end (B) is there anything that needs to be added for the 3900 series router? any advise on this will be much appreciated.

*Jun 15 11:44:04.155: %SYS-5-CONFIG_I: Configured from console by vty0 (172.20.45.51)
*Jun 15 11:44:22.099: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8 callref = 0x0047
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x91AA068001008201008B0100A11302017D06042B0C0900300880064578746E2031
        Calling Party Number i = 0x4980, '1201'
                Plan:Private, Type:Subscriber(local)
        Called Party Number i = 0x80, '8'
                Plan:Unknown, Type:Unknown
        High Layer Compat i = 0x9181
*Jun 15 11:44:22.099: ISDN Se0/0/1:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0x8047
        Channel ID i = 0xA98381
                Exclusive, Channel 1
*Jun 15 11:44:22.287: ISDN Se0/0/1:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0047
        Called Party Number i = 0x80, '2'
                Plan:Unknown, Type:Unknown
*Jun 15 11:44:22.539: ISDN Se0/0/1:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0047
        Called Party Number i = 0x80, '6'
                Plan:Unknown, Type:Unknown
*Jun 15 11:44:22.791: ISDN Se0/0/1:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0047
        Called Party Number i = 0x80, '8'
                Plan:Unknown, Type:Unknown
*Jun 15 11:44:24.043: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8047
*Jun 15 11:44:24.047: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8 callref = 0x8047
        Progress Ind i = 0x8188 - In-band info or appropriate now available
*Jun 15 11:44:32.731: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0047
        Cause i = 0x8090 - Normal call clearing
*Jun 15 11:44:32.731: ISDN Se0/0/1:15 Q931: TX -> RELEASE pd = 8 callref = 0x8047
*Jun 15 11:44:32.743: ISDN Se0/0/1:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0047

Amit Kumar · ‎06-15-2015

Hi,

Just to double check, have you enabled debug voip ccapi as well, as i do not see any output for CCAPI.

Also i would like to confirm if there is any other dial-peer having incoming called-number . configured. , as Overlap receiving timer will not come in to effect if this command, or any other dial peer in the call flow is associated with any application.

show run | s called-number

If you do not have an dial-peer i would request you to create an specific incoming dial-peer.

dial-peer voice <tag> pots

incoming called-number .T

direct-inward-dial

port 0/0/1:15

Thanks,

Amit

Kaushik Ray · ‎06-15-2015

!
dial-peer voice 1 pots
incoming called-number .T
!

there is the above configure but that is for the other E1 which uses trunk groups; could that affect as well?

Amit Kumar · ‎06-15-2015

Yes, this dial-peer can also match as an incoming dial-peer. I would also like to understand what is complete number dialed from Mitel Side, as in debug i can see that router waits for 2 seconds as per configuration, before sending callproc.

Last Digit from Mitel: 11:44:22.791

Call_Proc sent by gateway: 11:44:24.043 , Ideally Mitel should have sent an ISDN Sending Complete message.

Also please do let me know what is on other side of Gateway ? , are we using CME or CUCM.

Thanks,

Amit Kumar

*Jun 15 11:44:22.791: ISDN Se0/0/1:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0047
Called Party Number i = 0x80, '8'
Plan:Unknown, Type:Unknown - See more at: https://supportforums.cisco.com/discussion/12533361/cisco-message-call-cannot-be-completed-dialled-forwarding-calls#sthash.fsIvQCqb.dpuf

Kaushik Ray · ‎06-15-2015

Other side of the Gateway is another 29xx router connected to another MITEL pabx using an E1

From the other side when they do trunk dialling it can call out to site A without the message straight away; from this side when they call it comes back with the command wait and then establish the call

Amit Kumar · ‎06-15-2015

Ok, so its confirmed that only 4 digit number is dialed, and gateway is getting all 4 digits.

Please do help me with below said output.

show dial-peer voice summary

Also it would be good if you can share your complete configuration, you can hide ip address and other confidential information, as i need to co-relate configuration, if at any points called digits are getting manipulated or is there any outbound dial-peer available for match etc.

Thanks,

Amit

Kaushik Ray · ‎06-15-2015

A end

3000   voip up   up             9T                 0 syst ipv4:10.49.54.1
3001   voip up   up             [2-9]...           0 syst ipv4:10.49.54.1
1000   voip up   up             .                  2 syst ipv4:
1001   voip up   up             .                  1 syst ipv4:
2000   pots up   up             441224374190       1                      up   trunkgroup DDI1
2001   pots up   up             441224374191       2                      up   trunkgroup DDI2
2002   pots up   up             441224374192       3                      up   trunkgroup DDI3
2003   pots up   up             441224374193       4                      up   trunkgroup DDI4
2004   pots up   up             441224374194       5                      up   trunkgroup DDI5
2005   pots up   up             441224374195       6                      up   trunkgroup DDI6
2006   pots up   up             441224374196       7                      up   trunkgroup DDI7
2007   pots up   up             441224374197       8                      up   trunkgroup DDI8
2      voip up   down           .T                 0 syst
1      pots up   up                                0                      down
4000   pots up   up             1...               0                      up   0/0/1:15
4001   pots up   up                                0                      down 0/0/1:15

B end

             AD                                    PRE PASS                OUT
TAG    TYPE MIN OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT PORT    KEEPALIVE
4000   pots up   up             9T                 0                      up   0/0/0:15
3000   voip up   up             1...               0 syst ipv4:172.26.70.241
4001   pots up   up             [2-9]...           0                      up   0/0/0:15
2      voip up   down           .T                 0 syst
1      pots up   up                                0                      down

I have emailed you the configs

Amit Kumar · ‎06-15-2015

Ok, Thanks,

So side B is calling Side A , in failed scenario, right.

- Amit

Kaushik Ray · ‎06-15-2015

Could not find an direct message if you can share that please.

Calling from A to B works fine with but only after comes back with the command Cannot be called as dialled.

Calling from B to A works straight away. no issues at all

Amit Kumar · ‎06-15-2015

So you mean to say , that calls works fine, but at first you get an message that " call can not be completed as dialled ", then it goes through, and two parties are able to talk to each other.

Can you please enabled below said debugs, and perform a test call.

debug isdn q931

debug voip ccapi inout

debug voip dialpeer inout

Calling number :

called Number

Thanks,

Amit

Kaushik Ray · ‎06-15-2015

Yes call works absolutely fine, but initially comes back with that message and when you hold on to the call the other end starts ringing and both way conversation is done. This is from A to B.

B to A goes on straight away with out the message.

Attached are the configs for the A and B and debug for A and B

calling number 1201

Called number **2 0501 8268

Amit Kumar · ‎06-15-2015

While I go through configuration and debug output, can you please increase t302 timer to higher value, say 6000 msecs. Please perform shut / no shut on serial interface post changes.

Thanks,

Amit

Kaushik Ray · ‎06-15-2015

interface Serial0/0/1:15
A(config-if)#isdn overlap-receiving T302 6000
A(config-if)#
A(config-if)#shut
A(config-if)#no shut

B(config)#interface Serial0/0/0:15
B(config-if)#isdn overlap-receiving T302 6000
B(config-if)#shut
B(config-if)#no shut

Kaushik Ray · ‎06-16-2015

Apologies again, anything else I can try regarding this?

Thanks

Cisco Message " Call cannot be completed as dialled" before forwarding calls