Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
This section provides solutions to frequently asked questions (FAQs) about the
Spacevars | ||
---|---|---|
|
...
Table of Contents | ||
---|---|---|
|
...
Pagebreak |
---|
You can transfer files from one unit of a HA pair to the other (this comes in handy for large files that you may have to send over a slow VPN), using SCP and port 2024.
Beginning with release 3.1, file transfers must be performed using SFTP on port 2024. Use the following steps as a guide (default login/password is sftpadmin/sftpadmin):
"I'm moving my SBC 5k from one building to another and need to change my SFPs from copper to fibre. Can I just swap them with the Ribbon-provided SFPs before I power on the SBC, or is there more involved?"
You can swap the SFPs as long as you make sure to use the Ribbon-provided SFPs. Do not use a mix fiber and copper SFPs (all PKT ports have to be the same and all HA ports have to be the same).
You can transfer files from one unit of a HA pair to the other (this comes in handy for large files that you may have to send over a slow VPN), using SCP and port 2024.
Beginning with release 3.1, file transfers must be performed using SFTP on port 2024. Use the following steps as a guide (you can use any CLI account in the Administrator group):
Connect to target SBC. In this example, SBXa is the source and SBXb is the target SBC
Connect to target SBC. In this example, SBXa is the source and SBXb is the target SBC.
Code Block | ||
---|---|---|
| ||
sftpadmin@SBXa$ sftp -oPort=2024 sftpadmin@SBXb
Connecting to SBXb
sftpadmin@SBXb's password: sftpadmin
Connected to SBXb |
Use the put command to transfer a file to the specified directory as shown in the example below.
Code Block | ||
---|---|---|
| ||
sftp>admin@SBXa$ putsftp -oPort=2024 admin@SBXb Connecting to SBXb admin@SBXb's password: <password> Connected to SBXb |
Use the put command to transfer a file to the specified directory as shown in the example below.
Code Block | ||
---|---|---|
| ||
sftp> put sbc-V03.01.00-R000.sbc-V03.01.00-R000.x86_64.tar.gz /opt/sonus/external |
...
You can also do a search from the EMA GUI. To view the Routing workspace, see Call Routing: System Provisioning - Routing.
Caption | ||||
---|---|---|---|---|
| ||||
...
The SBC can cache Registration information by turning on the Trunk Group field "Require Registration". It is often useful to display the users that have successfully Registered.
Code Block | ||
---|---|---|
| ||
% show status addressContext default sipRegCountStatistics
% show status addressContext default sipActiveRegNameStatus |
Sometimes it is handy to test IP connectivity from the various interfaces on the SBC platform. Use the Ping utility from the EMA:
Note |
---|
In the above example, IP addresses are intentionally blurred. |
...
". It is often useful to display the users that have successfully Registered.
Code Block | ||
---|---|---|
| ||
% show status addressContext default sipRegCountStatistics
% show status addressContext default sipActiveRegNameStatus |
...
As a best practice, Sonus Ribbon recommends configuring one signaling port per zone. The SBC chooses a port (usually the first port) in the zone for outbound connections. However, the SBC cannot enforce the use of a specific signaling port within the zone to initiate a call on a trunk group. The trunk is assigned to a zone and not to a signaling port in the configuration model. To associate a unique source port for each trunk group, create separate zones defining a single signaling port per zone.
...
The OIDs are indexes in the MIB tables, and indexes are not readable using SNMP GET requests. The SNMP GETNEXT requests are used to find out what indexes are currently present in the MIB tables. For more information, refer to the section How to Retrieve Sonus Ribbon Enterprise MIB OIDs.
Pagebreak |
---|