cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
840
Views
0
Helpful
1
Replies

UC560/CCA2.2(5) Issue with XO SIP Configuration

Mario Garcia
Level 3
Level 3

Had an issue setting up XO SIP configuration on the UC560 using CCA2.2(5).  I was in the process of turning up a XO Communication SIP circuit.  Basically CCA was not sending the password correctly to the UC.  Had to configure the SIP password using CLI.  This has been reported to the CCA team.

1 Reply 1

Steven DiStefano
VIP Alumni
VIP Alumni

Thanks Mario,

CCA does not send the password as hidden when configuring this CLI.

CCA sends the plain text:

  authentication username password

The hidden password you are seeing is the default behavior of the CLI -- after the password is initially set from plain text, it will be hidden.  So when CCA reads it back, it is the hidden string only (the checkbox to view as plain text on the UI has meaning when entering the value for first time or making changes).

But in short, we have bug.  Upon edit of existing SIP Trunk configuration, changes to digest authentication username/password are only sent for username changes.  Password changes only are not detected.  The problem is in the backend, not the UI.

We are filing a bug so we can get it fixed in next release.  Workaround isremove the SIP Trunk with "None" option and then reconfigure. Note this is not specific to XO, but any SIP Trunk using Digest Authentication.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: