Methods used to handle abnormalities in network-wide orderwire phone dial-up

18

Question:
When a BWS 1600G system runs for a period, the orderwire phone of a site generates audio squealing, and no ringback tone is played back upon a call to another site. The orderwire phone is restored to normal after all system control boards at the sites are reset multiple times onsite. The same issue, however, occurs shortly again.
Analysis:
1. Run the :cfg-get-phonestat: OHPBid, telsrl command to check the network-wide orderwire phone status. It is found that all orderwire phones at the sites are in meeting state (the queried value is 13).
2. A system based on platform 5.0 cannot force orderwire phones to idle state.
3. When an NE on the network initiates a network-wide conference call,
but another NE at a site is reset or ends the call upon monitoring channel unavailability, other sites will be kept in meeting state and cannot exit.
Answer:
1. Initiate a network-wide conference call at the central site, and end the call after a period. (To counter interference, you can initiate the call multiple times.
2. Run the :cfg-get-phonestat: OHPBid, telsrl command to check the network-wide orderwire phone status. If value 0 is returned, the site has been restored to the idle state. If a site returns value 13, the site is in a conference call and the phone is not hung up properly. When this occurs, instruct the onsite engineers to hung up properly or reset the NE. When the site is restored, initiate a network-wide conference call at the central site, and end the call after a period. Then the orderwire phone at the site is restored to the idle state.
[Note]
1. This issue occurs on a network that uses an SCC board providing both the system control and orderwire service. BWS 320G NEs use separate OHP boards and therefore are not involved in this issue.
2. The following describes the :cfg-get-phonestat: OHPBid, telsrl command:
Parameter OHPBid: slot ID of the orderwire board
Parameter telsrl: Nth channel of orderwire phone (value 1 indicates the first channel for example)
Return value indication:
Orderwire phone status codes:
SPS_IDLE: 0x00 (idle)
SPS_PREDIAL: 0x01 (pre-dial)
SPS_DIAL: 0x02 (dialing)
SPS_ROUTES: 0x03 (addressing)
SPS_RING: 0x04 (ringing)
SPS_ALERT: 0x05 (alerting or ringback)
SPS_PRETALK: 0x06 (pre-talk)
SPS_TALK: 0x07 (talk)
SPS_PRERELEASE: 0x08 (pre-release)
SPS_BUSY: 0x09 (busy)
SPS_THROUGH: 0x0a (pass-through)
SPS_MEET: 0x0b (meeting)
SPS_MEETSTART: 0x0c (meeting start)
SPS_MEETTALK: 0x0d (meeting talk)
SPS_MEETEND: 0x0e (meeting end)
SPS_PRERELEASE2: 0x0f (pre-release)

Other related questions:
Methods used to handle abnormalities in network-wide orderwire phone dial-up
Question: When a BWS 1600G system runs for a period, the orderwire phone of a site generates audio squealing, and no ringback tone is played back upon a call to another site. The orderwire phone is restored to normal after all system control boards at the sites are reset multiple times onsite. The same issue, however, occurs shortly again. Analysis: 1. Run the :cfg-get-phonestat: OHPBid, telsrl command to check the network-wide orderwire phone status. It is found that all orderwire phones at the sites are in meeting state (the queried value is 13). 2. A system based on platform 5.0 cannot force orderwire phones to idle state. 3. When an NE on the network initiates a network-wide conference call, but another NE at a site is reset or ends the call upon monitoring channel unavailability, other sites will be kept in meeting state and cannot exit. Answer: 1. Initiate a network-wide conference call at the central site, and end the call after a period. (To counter interference, you can initiate the call multiple times. 2. Run the :cfg-get-phonestat: OHPBid, telsrl command to check the network-wide orderwire phone status. If value 0 is returned, the site has been restored to the idle state. If a site returns value 13, the site is in a conference call and the phone is not hung up properly. When this occurs, instruct the onsite engineers to hung up properly or reset the NE. When the site is restored, initiate a network-wide conference call at the central site, and end the call after a period. Then the orderwire phone at the site is restored to the idle state. [Note] 1. This issue occurs on a network that uses an SCC board providing both the system control and orderwire service. BWS 320G NEs use separate OHP boards and therefore are not involved in this issue. 2. The following describes the :cfg-get-phonestat: OHPBid, telsrl command: Parameter OHPBid: slot ID of the orderwire board Parameter telsrl: Nth channel of orderwire phone (value 1 indicates the first channel for example) Return value indication: Orderwire phone status codes: SPS_IDLE: 0x00 (idle) SPS_PREDIAL: 0x01 (pre-dial) SPS_DIAL: 0x02 (dialing) SPS_ROUTES: 0x03 (addressing) SPS_RING: 0x04 (ringing) SPS_ALERT: 0x05 (alerting or ringback) SPS_PRETALK: 0x06 (pre-talk) SPS_TALK: 0x07 (talk) SPS_PRERELEASE: 0x08 (pre-release) SPS_BUSY: 0x09 (busy) SPS_THROUGH: 0x0a (pass-through) SPS_MEET: 0x0b (meeting) SPS_MEETSTART: 0x0c (meeting start) SPS_MEETTALK: 0x0d (meeting talk) SPS_MEETEND: 0x0e (meeting end) SPS_PRERELEASE2: 0x0f (pre-release)

Whether the USG6000 supports using an Android mobile phone for SSL VPN dial-up
No. You are advised to use the L2TP software provided by the PC to dial up to the intranet.

Can an outbound interface be specified for dial-up in the resource-shared DCC dial-up method
Yes. You can run the dialer route ip next-hop-address user hostname | broadcast * dial-string autodial | interface interface-type interface-number * command to specify an outbound interface for dial-up.

Does the USG6000 support dial-up SSL VPN with an Android phone
Don't support, it is recommended that users use the PC comes with L2TP software for dial-up access network.

Configuration of the Client-Initialized VPN on the USG2000 and USG5000
The method used to configure the Client-Initialized VPN on the USG2000 and USG5000 is as follows: The LAC client can directly initiates a tunnel establishment request to the LNS bypassing the LAC. The LNS allocates an address to the LAC client. The HQ network can connect to the Internet through the LNS. An employee on a business trip can directly initiate a tunnel establishment request to the LNS by means of L2TP dialup. The L2TP client software must be installed on the PC of the employee. Configure the Client-Initialized VPN using the CLI: 1. Configure the LNS. a. Create and configure the virtual interface template. [LNS] interface virtual-template 1 [LNS-Virtual-Template1] ip address 192.168.0.1 255.255.255.0 [LNS-Virtual-Template1] ppp authentication-mode chap [LNS-Virtual-Template1] quit b. Enable the L2TP. [LNS] l2tp enable c. Create and configure the L2TP group. [LNS] l2tp-group 1 d. Configure local tunnel name on the LNS end and the received peer tunnel name. [LNS-l2tp1] tunnel name LNS [LNS-l2tp1] allow l2tp virtual-template 1 [LNS-l2tp1] tunnel authentication [LNS-l2tp1] tunnel password cipher Password123 Note: If you use the L2TP client software provided by the Windows system to dial up, you must disable the L2TP tunnel verification function. e. Define an address pool and allocate an IP address to the dial-up user. [LNS] aaa [LNS-aaa] ip pool 1 192.168.0.2 192.168.0.100 f. Set the user name and password (consistent with those configured on the PC of the employee on a business trip). [LNS-aaa] local-user vpdnuser password cipher Hello123 [LNS-aaa] quit Note: Because the addresses in the IP address pool are not in the same network segment as the intranet addresses, you need to configure the route to network segment 192.168.0.0 on the HQ device, and set the next hop address to 192.168.1.1. g. Allocate an address in the IP address pool to the peer interface. [LNS] interface virtual-template 1 [LNS-Virtual-Template1] remote address pool 1 [LNS-Virtual-Template1] quit

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top