phones cannot make outgoing calls through voice gateway ISR 4400 serie

[DAK007]

Hello , 

we are replacing the old voice gateway a cisco 3900 by a new isr 4400 series, it was working fine with the of one but after making the transcript on the new one we see this errors on the logs :

025893: Oct 25 2023 19:39:16.982 GMT: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_reg_search_call_id_table:
No entry found in sipCallID Table
025894: Oct 25 2023 19:39:16.982 GMT: //6119/04BE37D8984B/SIP/Error/ccsip_spi_register_incoming_unregistration:
CCSIP_REGISTER:: no registration found
025895: Oct 25 2023 19:39:16.983 GMT: //6119/04BE37D8984B/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 10.16.111.159:5060;branch=z9hG4bK0ee01402
From: <sip:8389213@10.16.254.24>;tag=08cc68e91a8f866621384503-50173223
To: <sip:8389213@10.16.254.24>;tag=1A497A61-12F3
Date: Wed, 25 Oct 2023 19:39:16 GMT
Call-ID: 08cc68e9-1a8f0384-5f208ac0-6b3dc7ae@10.16.111.159
Server: Cisco-SIPGateway/IOS-17.3.5
CSeq: 32153 REGISTER
Content-Length: 0

025896: Oct 25 2023 19:39:17.957 GMT: //6086/F2402E12982A/SIP/Error/sipSPIFlushDeferredQueue:
Invalid deferredQueue
025897: Oct 25 2023 19:39:18.060 GMT: //6087/F2500E88982B/SIP/Error/sipSPIFlushDeferredQueue:
Invalid deferredQueue
025898: Oct 25 2023 19:39:18.877 GMT: //6088/F2CCB6FF982C/SIP/Error/sipSPIFlushDeferredQueue:
Invalid deferredQueue
025899: Oct 25 2023 19:39:18.982 GMT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REGISTER sip:10.16.254.24 SIP/2.0
Via: SIP/2.0/UDP 10.16.111.159:5060;branch=z9hG4bK0ee01402
From: <sip:8389213@10.16.254.24>;tag=08cc68e91a8f866621384503-50173223
To: <sip:8389213@10.16.254.24>
Call-ID: 08cc68e9-1a8f0384-5f208ac0-6b3dc7ae@10.16.111.159
Max-Forwards: 70
Date: Wed, 25 Oct 2023 19:39:10 GMT
CSeq: 32153 REGISTER
User-Agent: Cisco-CP9971/9.3.2
Contact: <sip:f77a3a5e-fa55-3ad3-b779-fcd6db97f048@10.16.111.159:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-08cc68e91a8f>";+u.sip!devicename.ccm.cisco.com="SEP08CC68E91A8F";+u.sip!model.ccm.cisco.com="493"
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-6.0.0,X-cisco-xsi-8.0.1
Content-Length: 0
Expires: 0

[Carlo Poggiarelli]

Hi,

Are you using it as VG only or as CME?

It would be useful if you could post the entire 44xx configuration and a complete debug ccsip message log so I can give a look .

Please let me know .

Regards 

Carlo

[DAK007]

Hello Carlo,

thank you for you response, I'm attaching the show run and the logs of the isr 4400

[Rajan]

Hi,

You have allowed only subnet 10.16.111.0 in the voice register pool but I could see registration requests from other subnets as well whcih will get rejected.

voice register pool 1
id network 10.16.111.0 mask 255.255.255.0

For example below:

014307: Oct 25 2023 19:06:11.693 GMT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REGISTER sip:10.16.254.24 SIP/2.0
Via: SIP/2.0/UDP 10.16.110.170:5060;branch=z9hG4bK3b68ab7a
From: <sip:8389355@10.16.254.24>;tag=88908d6945772d671793888a-346c81e1
To: <sip:8389355@10.16.254.24>
Call-ID: 88908d69-4577002a-023c6ea8-54444663@10.16.110.170
Max-Forwards: 70
Session-ID: 102a2e7800105000a00088908d694577;remote=00000000000000000000000000000000
Date: Wed, 25 Oct 2023 19:06:01 GMT
CSeq: 11024 REGISTER
User-Agent: Cisco-CP7821/14.0.1
Contact: <sip:212a9b37-ecf2-16cd-36b2-b920656da800@10.16.110.170:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-88908d694577>";+u.sip!devicename.ccm.cisco.com="SEP88908D694577";+u.sip!model.ccm.cisco.com="621"
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Content-Length: 0
Expires: 0

=================================================================

For the registration requests from valid subnet "10.16.111.0", can you please try adding "number" command in the voice register pool to see whether it helps.

voice register pool 1
number 1 8389...

HTH
Rajan
Please mark all useful posts as helpful and solutions as accepted wherever applicable

[DAK007]

hello Raja,

thank you for the response.

phones are grouped per vlans, and  there  is a DHCP which provide IP's base on vlans

ip dhcp pool vlan_voip_hq_8
network 10.16.109.0 255.255.255.0
dns-server 10.16.1.18
default-router 10.16.109.253
domain-name xxx
option 150 ip 10.16.149.44 10.16.149.35
lease 8
!
ip dhcp pool vlan_voip_hq_5
network 10.16.110.0 255.255.255.0
dns-server 10.16.1.18
default-router 10.16.110.253
domain-name xxx
option 150 ip 10.16.149.44 10.16.149.35
lease 8
!
ip dhcp pool vlan_voip_hq_2
network 10.16.102.0 255.255.255.0
dns-server 10.16.1.18
default-router 10.16.102.253
domain-name xxx
option 150 ip 10.16.149.44 10.16.149.35
lease 8
!
ip dhcp pool vlan_voip_hq_12
network 10.16.112.0 255.255.255.0
dns-server 10.16.1.18
default-router 10.16.112.253
domain-name xxx
option 150 ip 10.16.149.44 10.16.149.35
lease 8
!
ip dhcp pool vlan_voip_hq_3
network 10.16.111.0 255.255.255.0
dns-server 10.16.1.18
default-router 10.16.111.253
domain-name xxx
option 150 ip 10.16.149.44 10.16.149.35
lease 8
!

[Carlo Poggiarelli]

Hi,

Thanks for the logs.

As I cannot see any calls arriving to your Cube, can you confirm that you captured the debug while making an outgoing call?

I see some communications error coming from subnet 10.16.111.0 trying to register to the Cube and I wonder to know if you are using your router as Cube or CUCME.

Please elaborate more how you would deploy your router and, in the meanwhile, add the following line to your config:

voice service voip

ip address trusted list

ipv4 10.16.0.0 255.255.0.0

Please let me know

Regards

Carlo

[DAK007]

i copied also the show run of the 3900, actually configuration works with the 3900 router call goes out through the 3900 perfectly. we have both version 9 in cluster  and version 14 in cluster and migrating all phones that are located on the version 9 cluster  to the version 14 cluster more than 50% are already migrated.

we use the gateway for outgoing call like mobile or internationals calls inside calls goes through SIP truck 

the publisher of the v9 ip is  10.16.149.35

the subscriter of the v9 ip is 10.16.149.36

the publisher of V14 ip is  10.16.149.44

the subscriber of the v14 ip  is 10.16.5.63

due to high traffic we can try swap only the afternoon so will try the command 

ip address trusted list

ipv4 10.16.0.0 255.255.0.0

do you have any more advice for me? it is very urgent !!

thank you 

[DAK007]

yes I captured log during calls but calls are refused when they reach the gateway

[Carlo Poggiarelli]

Did you configure your VG as SIP Trunk or H323 gateway on your CUCM 14 cluster?

[DAK007]

from Device -> Gateway , 

i see H323 , see screenshot

[DAK007]

hello,

the problem is not resolve, 

 - i have disabled fraud-toll with 

voice service voip
 no ip address trusted authenticate

 - i had 

voice register pool 1
number 1 8389...

still same issue, any other advice

[Carlo Poggiarelli]

Ok so you have an H323 gateway.

I suggest you to convert it to a sip trunk as soon as you can.

To troubleshoot your issue, please activate a debug voip dialpeer inout and place a call and then send the output.

Thanks 

Regards

Carlo

[DAK007]

Hello problem solved, 

the transcription rule for mapping :

- the outgoing calls groing from cucm -> gateway ->  PSTN

and

- incoming calls PSTN -> Gateway -> CUCM

was  not correct for the specific number we adjusted and problem solved