Hi, i´ve the problem on my 1760 that calling out the ISDN-line from a fxs-port attached analog phone there is no Calling-ID presented in the call setup of the router bri-interface. I verified that with deb isdn q931. Using a VOIP-dial-peer it is presented.
I used IOSes 12.3(6);12.3(4)T3;12.3(7)T. All the same.
The miracle is that in the headquarter there is a 3640, also with the same isdn-vic which presents the calling-id and i can´t see a difference in the commands of the voice-ports and dial-peers. The headqarter-router is a 3640 with with 12.3(4)T and Call-manager express with IP-Phones and ATA-Box, no FXS in the router. This is the only difference I see. The 1760 has local FX-S ports, the 3640 has IP-Phones and ATA-Box.
I tried a couple of commands like no caller-id block or no clid strip and so on, but nothing worked. Also show-commands show up that there is no call-blocking configured anyhow.
Here is additionally a debug output from "debug translation detail" and "debug isdn q931". Although there is no translation rule aplied it shows that there originaly was a caller-id which magicaly is not used by the isdn bri:
Following output is generated from "debug isdn events detail" it shows that for any reason the router believes this is a private call. By the way the problem exists only by calling from a locally attached FXS port through ISDN. Calling from a VOIP Dialpeer the Calling-number is correctlx displayed!
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...