I noticed a post questioning if it was possible to recieve caller id on a FXS/DID port in DID mode...I have this implemented and do not see caller id..is this a limitation of the card or is it possible?
The [no] caller-id enable command enables or disables the transmission of Caller ID on an FXS port, and enables or disables reception of Caller ID on an FXO port.
Issue the [no] caller-id enable command to enable the Caller ID name for inbound PSTN calls on the FXO port.
You must configure the alerting method when the Caller ID standard, specified by locale through the cptone command, is not Bellcore/Telcordia. If you do not configure the alerting method, the default caller-id alerting ring 1 command is applied. The command that you enter is determined by the Bellcore/Telcordia or ETSI standard that your service provider uses for Caller ID.
Thanks for your reply...I have no issues with the caller-id command on a FXO or FXS card...but when you use the FXS in DID mode the command is not available. I assume this is a limitation of the card. Please let me know your thoughts...
I'm attempting the same implementation- I've run into this once before where the carrier states they do not pass caller-id on analog DIDs. (This was SNET/SBC last year; and now a telco in Northern Pittsburgh). I, too, can not enable/disable caller-id on the sub interface. I'm assuming everything is OK on my end and it is the fact, as stated by telco, that they do not pass the info.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...