Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <[email protected]> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <55618> Message-ID: <[email protected]>
While I am new to sipXecs, I have lots of experience with IP telephony... the problem has not changed. I was trying to show examples where the caller-id was being set and those were it was not. The ITSP is Vitelity. The version is 4.2.1-018971.dhubler. Here are some scenarios: - "Default Caller ID" is set on the gateway. This caller ID number is used. *WORKS* - "Default Caller ID" is set on the gateway. A more specific caller-id is set on the user. There are NO other items set on the gateway caller-id. The default caller ID is used instead of the more specific user caller ID. *NO WORKS* - "Specify Caller ID" is set on the gateway all other settings are overwritten and the "Specify Caller ID" setting is used. *WORKS* Here is what I want to work: - ONLY "Transform extension" is set Caller ID prefix is filled in with the preceding 6 digits with the Keep digits set to 4. The outbound caller ID will be 1XXXX where XXXX is the extension. The tranform is not working. *NO WORKS* In ALL CASES the outbound caller-id is being set. So this has NOTHING to do with the ITSP. I have verified in the logs that the ID being sent out is the same as what shows up on the receiving end. Roy _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
