Incoming call not landing on IP phones using CUCM

[Mayank Nauni]

Hi all,

I am facing an issue; the incoming calls are not landing on the IP phones using the CUCM, below is the debug for the same and it shows the cause as Unallocation/Unassigned number.

I checked the config of Gateway, route pattern, partitions and CSS but seems to be ok.

.Jan  3 17:01:44.977: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=93 nr=117
.Jan  3 17:01:44.977: ISDN Se0/0/0:15 Q931: SETUP pd = 8  callref = 0x017B
         Sending Complete
         Bearer Capability i = 0x8090A3
                 Standard = CCITT
                 Transfer Capability = Speech
                 Transfer Mode = Circuit
                 Transfer Rate = 64 kbit/s
         Channel ID i = 0xA98381
                 Exclusive, Channel 1
         Calling Party Number i = 0x0083, '0162508156'
                 Plan:Unknown, Type:Unknown
         Called Party Number i = 0x81, '1065'
                 Plan:ISDN, Type:Unknown
.Jan  3 17:01:44.981: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=94
.Jan  3 17:01:44.981: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x817B callID = 0x00F5 switch = primary-net5 interface = User
.Jan  3 17:01:44.985: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=117 nr=94
.Jan  3 17:01:44.985: ISDN Se0/0/0:15 Q931: CALL_PROC pd = 8  callref = 0x817B
         Channel ID i = 0xA98381
                 Exclusive, Channel 1
.Jan  3 17:01:44.985: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=118 nr=94
.Jan  3 17:01:44.985: ISDN Se0/0/0:15 Q931: DISCONNECT pd = 8  callref = 0x817B
         Cause i = 0x8081 - Unallocated/unassigned number
.Jan  3 17:01:44.993: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=118
.Jan  3 17:01:44.997: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=119
.Jan  3 17:01:45.037: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=94 nr=119
.Jan  3 17:01:45.037: ISDN Se0/0/0:15 Q931: RELEASE pd = 8  callref = 0x017B
.Jan  3 17:01:45.037: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=95

Any suggestions?

Regards,

Mayank

[Mayank Nauni]

I have modified the existing VOIP dial-peer as suggested but the issue still persists

[Gajanan Pande]

How does the new dial-peer config looks now ? Pls post only that dial-peer config.

What is the DN range assigned to your phones ? If you have DID range 1000 to 1599, you should either have the same DN range or have a translation pattern to convert those DIDs to your DN range. Pls confirm if such config is in place in your CUCM.

GP.

[Mayank Nauni]

Hi,

Please find the responses below :-

dial-peer voice 2 voip

preference 2

destination-pattern 1...

session target ipv4:10.3.3.11

incoming called-number .T

voice-class codec 100 

dtmf-relay h245-alphanumeric

no vad

I will be attaching the translation pattern shortly.

[Gajanan Pande]

also try removing " incoming called-number .T " from the DP. This will also work only if you have proper DN range or Translation pattern configured in CUCM

GP.

[baris]

If there are multiple interfaces on the gateway, can you check whether you added a bind command for the interface (ip address) that is configured as the h.323 gateway in call manager?

Gateway(config-if)#h323-gateway voip bind srcaddr X.X.X.X

Sent from Cisco Technical Support iPad App

[Mayank Nauni]

Hi Baris,

It is already done... thanks for highlighting.

Please also let us know what would be the CSS on gateway for called and calling party, same as phones or something different?

Regards,

Mayank

[Gajanan Pande]

CSS can be different, just ensure that the partitions in which your phones are, shd be included in gateway's CSS. Same to be done for phone CSS too ( include gateway partitions ). You can play with partitions & CSS.

GP.

[Mayank Nauni]

One quick query ....

If my interface's IP address is 192.168.1.1 which is the gateway ... will that be the srcaddr in the suggested command below?

Gateway(config-if)#h323-gateway voip bind srcaddr X.X.X.X

[Gajanan Pande]

correct.

[Mayank Nauni]

"also try removing " incoming called-number .T " from the DP. This will also work only if you have proper DN range or Translation pattern configured in CUCM"

Did the same... no improvements!

[Gajanan Pande]

As I said, it will work only if you have the DID range as extension numbers ( DN ) or there is a proper translation pattern in place to translate your DID range to DN range. I dont see any details from you on this point.

GP.

[Mayank Nauni]

Hi Mr. Pande,

The translation pattern is displayed in the *.doc attachement above, is this what you are looking for?

Regars,

Mayank Nauni

[Gajanan Pande]

Hi Mayank,

What is your DN range ?

I see a Translation pattern for 1xxx, which translates to a big number, are you using E.164 DN plan ?

GP.

[Mayank Nauni]

DID range is 327731000 to 327731599 and we have given 4 digit DN to IP phones e.g 10000, 1001, 1002.

"I see a Translation pattern for 1xxx, which translates to a big number, are you using E.164 DN plan ?"

I am not sure about it ... can you suggest me how to find it out?

[Gajanan Pande]

Remove your translation pattern " 1xxx " from CUCM & it should fix it.

GP.