Outgoing calls to PSTN via BRI trunks not using DID but SPID for CLID ??
I have a customer who has multiple BRI trunks to the PSTN (used for outbound calling. Class 5 is DMS100).
The customer also has a number of DID on the callmanager side serviced by Analog DID Trunks (inbound to CallManger). When an IP Phone calls an external PSTN destination, the destination called party recevies the SPID of the BRI port as the Caller ID even though we are sending the actual DID as the source calling number (Shown below. Numbers changed to protect identity of customer):
The config on the BRI port is as follows (again SPID numbers changed by me):
no ip address
isdn switch-type basic-ni
isdn spid1 XXXYYY943000 XXXYYY9430
isdn spid2 XXXYYY943100 XXXYYY9431
isdn incoming-voice voice
The service provider has told us this is standard and typical as they are trying to protect toll fraud and has implications for 911 and some more reasons... I have to think this is incorrect. Anyone have any expierence here with this?
Re: Outgoing calls to PSTN via BRI trunks not using DID but SPID
Thanks for the info (I have already read that Tech Tip). I do appreciate the comments. Anyone in North America connected to a DMS 100 via BRI able to send PSTN callers the actual DID on the Cisco IP Phone versus the SPID?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.