Are you using FQDN for your CUCM servers ? I remember a couple of defects that affect some SIP Phones not able to register back to CUCM post SRST. I will add them here if I find them. ... View more

Working asa designed. Once the call has been answered by the CUC call handler, a "200 OK" marks the dialog establishment. With SIP, none of the devices will send a '"180" or "183" in-dialog. A couple of workarounds - 1. Invoke Annunciator on CUCM for proxy ring back. 2. Use H.323. ... View more

I believe it should just have the patch for the part of code vulnerable and no other changes hence the reason for no readme either. ... View more

Can you share ANI, DNIS and RDNIS info please ? ... View more

This one's strange, if I am not missing anything. I see the DTMF being received but the DSP's never detect it/generate them and pass them over VTSP to be delivered out - Jun 24 11:00:07.702: //17237/8ACAF1079174/DSPAPI/[0/1:1]/dsp_vq_stats: Jun 24 11:00:10.394: s=VoIP d=DSP payload 0x65 ssrc 0xA95D989C sequence 0x6CD0 timestamp 0x72D638EF Jun 24 11:00:10.394: <<<Rcv> Pt:101 Evt:4 Pkt:09 00 00 Jun 24 11:00:10.414: s=VoIP d=DSP payload 0x65 ssrc 0xA95D989C sequence 0x6CD2 timestamp 0x72D638EF Jun 24 11:00:10.414: <<<Rcv> Pt:101 Evt:4 Pkt:09 00 A0 Jun 24 11:00:10.434: s=VoIP d=DSP payload 0x65 ssrc 0xA95D989C sequence 0x6CD4 timestamp 0x72D638EF Jun 24 11:00:10.434: <<<Rcv> Pt:101 Evt:4 Pkt:09 01 40 Jun 24 11:00:10.454: s=VoIP d=DSP payload 0x65 ssrc 0xA95D989C sequence 0x6CD6 timestamp 0x72D638EF Jun 24 11:00:10.454: <<<Rcv> Pt:101 Evt:4 Pkt:09 01 E0 Jun 24 11:00:10.474: s=VoIP d=DSP payload 0x65 ssrc 0xA95D989C sequence 0x6CD8 timestamp 0x72D638EF Jun 24 11:00:10.474: <<<Rcv> Pt:101 Evt:4 Pkt:09 02 80 This is all I see. Payload is good and the events are correct. I should see something like - Jun 24 10:59:48.170: //17237/8ACAF1079174/DSPAPI/[0/1:1]/dsp_voice_gen_dial_digit: direction=1 count=13 type=0 [0] 2 components, Frequency - 941/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [0] 2 components, Frequency - 941/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [3] 2 components, Frequency - 697/1477(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [1] 2 components, Frequency - 697/1209(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [2] 2 components, Frequency - 697/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [0] 2 components, Frequency - 941/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [7] 2 components, Frequency - 852/1209(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [9] 2 components, Frequency - 852/1477(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [6] 2 components, Frequency - 770/1477(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [5] 2 components, Frequency - 770/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [3] 2 components, Frequency - 697/1477(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [6] 2 components, Frequency - 770/1477(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) [5] 2 components, Frequency - 770/1336(hz), Amplitude - 6544.6/6546.7(dBm0), On/Off time - 100/100(ms) Jun 24 10:59:48.170: //17237/8ACAF1079174/HPI/[0/1:1]/hpi_voice_gen_dial_digit: This is for when the international number is dialed. Digits are generated/detected correctly and relayed. A couple of questions - 1. Is this an issue with International calls only ? 2. How about incoming calls, does DTMF work ? 3. What happens when you call from a SCCP phone, does DTMF work ? If you haven't tested the above scenarios, please test them and let me know the result. ... View more

Are you matching correct dial-peers which have the block translations ? Grab the following - debug voice ccapi inout debug voip trans debug ccsip mess ... View more

Sounds like a DTMF mismatch happening somewhere on the call flow. Check the DTMF configurations and settings on CUCM trunks, if in use. ... View more

Have you checked with debugs if you are getting the correct ANI that you are trying to block from the IOS perspective ? Also, are you hitting the correct dial-peer(s) that has the call block ? ... View more

I will check this out today. ... View more

The logs that you collected were with the correct config or corrected the confiig after reading my post ? ... View more

Didn't go through the logs but I will point out a couple of things - 1. Phone Proxy only supports 1024 bit encryption. 2. Ensure you don't have a SIP trunk on CUCM pointing to the CORE IP of CUBE. Registrations will be rejected. Additionally, there are concerns regarding your phone proxy config. I am highlighting them below - voice-phone-proxy cube01 tftp-server address ipv4 <cucm_ip> local-addr ipv4 <local_ip> acc-addr ipv4 <pub_ip> ctl-file ctl_secure access-secure service-map server-addr ipv4 <cucm_ip> port 8443 acc-addr ipv4 209.29.5.21 port 8443 service-map server-addr ipv4 <cucm_ip> port 8080 acc-addr ipv4 209.29.5.21 port 8080 service-map server-addr ipv4 <cucm_ip> port 3804 acc-addr ipv4 209.29.5.21 port 3804 complete voice-phone-proxy tftp-address ipv4 <local_ip> port-range 30000 60000 voice-phone-proxy tftp-address ipv4 <pub_ip> port-range 30000 60000 <local_ip> needs to be replaced with a CUBE core IP <pub_ip> needs to be replaced with the CUBE access IP acc-addr ipv4 209.29.5.21 >> this needs to be CUBE access IP These changes need to be made throughout the config including dial-peers and sip uri. In case you are wondering what the CORE and ACCESS ip addresses need to be - CORE IP is the internal CUBE address used to connect to CUCM ACCESS IP is for the interface that the remote phones will connect to. ... View more

SRST is tied to the SRST Reference that is configured on your device pools and pulled by the phones through the config file. Not sure why are you checking "Gateways" page on CUCM for SRST. Non-SRST, a voice router will take calls from CUCM. In SRST, the phone register to that very voice router and provide calling functionality in the absence of CUCM. ... View more

What do you mean by "srst devices are not listed as gateways" ? You would already have a dial plan on your IOS router to cater calls. The same dial-plan would be used when your phones failover to the router during SRST. ... View more