"When you are using FXO and FXS ports to set up connections to a PBX it is important to remember that FXS ports SEND caller ID and FXO ports RECEIVE caller ID. Because of this relationship caller ID is sent only one way when used on this type of connection - from FXS to FXO"
Now the quote above refers to PBX's but I am presuming the same rule applies with any FXO port on a voice gateway RECEIVING caller ID info FROM a FXS port on a Telco switch.
I understand you use the "station-id" command to configure a station name and number for Caller ID purposes.
What doesn't make sense to me it that on my 2801's this option can seemingly be configured on both FXS... AND FXO ports.
My question is why is it an option on FXO ports?? I can understand it being an option with the FXS ports because the SEND it out but if FXO ports only ever RECEIVE the information why would you ever need to configure the "station-id" command on an FXO port?
No doubt I'm missing something here but any help would be appreciated.
Re: Clarification of FXO port behavior with Caller ID
Thanks for the response (and testing!) on this. So just to clarify is appears the station-id coming from the PSTN is over-written by the FXO port if the "Station ID" command is configured on it and your testing appears to bear that out. Not clear on what you mean in your last sentence though?
I suppose I'm just wondering why someone would want to overwrite the caller ID coming in from the PSTN but I guess that's another story...
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...
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 discusses the bas...