We are having problems using a postage meter in a new SIP trunk deployment. The ATA 186 has a line that is shared by a fax machine and a Pitney Bowes DM100i postage meter. Faxes are mostly working fine - we turned down the baud rate to 9600 and turned off ECM, but the postage meter will not complete its negotiation. PB support either can't or won't tell me what the baud rate is on the meter, nor whether or not it can be adjusted. Someone had to take it home to upload the postage last week. Not a good solution going forward. We are really interested in working out the bugs in this deployment as the SIP trunk could help us save some money. Any ideas or suggestions? Thanks.
Like other IP devices, the Cisco ATA receives its configuration file and list of Cisco Unified CallManagers from the TFTP server. If the TFTP server does not have a configuration file, the Cisco ATA uses the TFTP server name or IP address and port number as the primary Cisco Unified CallManager name or IP address and port number.
After the Cisco ATA initializes, both ports on the Cisco ATA (skinny clients) attempt to connect with the primary Cisco Unified CallManager. If the connection or registration fails, the Cisco ATA skinny clients attempt to register with the next Cisco Unified CallManager in the Cisco Unified CallManager list. If that connection fails, the Cisco ATA skinny clients attempt to register with the last Cisco Unified CallManager in the list. If all attempts to connect and register with a Cisco Unified CallManager fail, the client attempts to connect at a later time.
Upon successful registration, the Cisco ATA client requests the Cisco Unified CallManager software version, current time and date, line status, and call forward status from the Cisco Unified CallManager. If the Cisco ATA loses connection to the active Cisco Unified CallManager, it attempts to connect to a backup Cisco Unified CallManager in the Cisco Unified CallManager list. When the primary Cisco Unified CallManager comes back online, the Cisco ATA attempts to reconnect to it.
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.