Why a SIP AG user communicate fail with a PBX user

13

A SIP AG is similar to a voice gateway connected to a PBX, and a SIP AG user is registered with the SIP server on the PBX. That is, the SIP AG user is similar to a SIP UE user on the PBX.
When a SIP AG user calls a PBX user, you need to correctly configure call prefixes. The inter-office trunk does not need to be configured.
Assume that a SIP AG user's number is 2200 and a PBX user's number is 1100. The local call prefixes 11 and 22 need to be set.
- Check the SIP AG configuration.
1. Check whether the SIP AG interface configuration is correct and whether the registration status is normal.
2. Check whether the user configuration on the SIP AG interface is correct.
3. Check whether the FXS interface on the SIP AG is normal.
- Check the PBX configuration.
1. Check whether the SIP server configuration is correct and whether the SIP server status is normal.
2. Check whether the prefix configuration is correct.
3. Check whether the SIP AG user is registered.
4. Check whether the SIP AG user configuration on the PBX is correct.
5. Check whether the license is valid.

Other related questions:
A SIP AG user fails to call a PBX user
A SIP AG is similar to a voice gateway connected to a PBX, and a SIP AG user is registered with the SIP server on the PBX. That is, the SIP AG user is similar to a SIP UE user on the PBX. When a SIP AG user calls a PBX user, you need to correctly configure call prefixes. The inter-office trunk does not need to be configured. Assume that a SIP AG user's number is 2200 and a PBX user's number is 1100. The local call prefixes 11 and 22 need to be set. Check the SIP AG configuration. 1. Check whether the SIP AG interface configuration is correct and whether the registration status is normal. 2. Check whether the user configuration on the SIP AG interface is correct. 3. Check whether the FXS interface on the SIP AG is normal. Check the PBX configuration. 1. Check whether the SIP server configuration is correct and whether the SIP server status is normal. 2. Check whether the prefix configuration is correct. 3. Verify that the SIPAG server has registered. 4. Verify that the SIPAG user on the PBX has been configured correctly. 5. Verify that the license is valid.

SIP users fail to be registered after outbound NAT is configured and canceled on the public network interface of the AR
Q: SIP users fail to be registered after outbound NAT is configured and canceled on the public network interface of the AR. A: SIP users connect to the SIP server through the AR enabled with outbound NAT. The ALG function is disabled for SIP, so STP packets cannot traverse the NAT device. As a result, the SIP server cannot communicate with SIP users and SIP users fail to be registered. When registration request packets of SIP users pass through the AR, the AR generates NAT session entries to record packet information and updates entries and the aging time after new packets are received. After the aging time is reached, the NAT session entries that fail to be updated are automatically cleared. Therefore, the SIP users that fail to be registered continue to send registration request packets. NAT session entries cannot be directly cleared after outbound NAT is canceled, and are automatically cleared after the aging time is reached. Because SIP users continuously send registration request packets, the AR continuously update NAT session entries and theaging time. That is, the NAT session entries cannot be automatically cleared. As a result, the SIP users fail to be registered. Run the nat alg command to enable ALG for SIP so that the SIP server can communicate with SIP users after outbound NAT is configured. In addition, run the reset nat session all command to forcibly clear the NAT session entries and quickly change the NAT configuration. Or, you can run the reset nat session all command to forcibly clear NAT session entries after outbound NAT is canceled, so that the SIP server can communicate with SIP users. Note: Deleting NAT mapping entries may affect exchange of some packets.

What are SIP AGs and PBXs, and what are the differences between them
Access devices on the IP Multimedia Subsystem (IMS) provide various access modes and convert various services into a uniform format that can be transmitted. On the IMS, an access device is called access gateway (AG). AGs play an important role on the IMS and are connected to users. AGs and media gateway controllers (MGCs) use Session Initiation Protocol (SIP). SIP-based AGs are called SIP AGs. A traditional private branch exchange (PBX) manages the incoming and outgoing calls of an enterprise. It connects the enterprise to the Public Switched Telephone Network (PSTN) and provides services for devices such as telephones, fax machines, and modems. It allows users in the enterprise to call each other using extension phones and routes inter-office calls to the PSTN through a trunk line. Traditional PBXs cannot meet the requirements of computer telephony integration (CTI) and voice over IP (VoIP). In addition, these PBXs are expensive and do not use standard and open platforms, creating difficulties in interconnecting PBXs of different vendors. IP PBXs overcome the limitations of traditional PBXs. IP PBXs are based on the IP protocol and provide both local exchange and IP user access functionality. IP PBXs integrate the voice communications system of an enterprise into the enterprise's data network so that the enterprise can build a uniform voice and data network connecting branches, offices, and staff around the world. The AR1200/2200/3200 can function as a PBX to provide traditional PBX functions and IP PBX functions. SIP AGs and PBXs have the following differences: -PBXs have two functions. PBXs can serve as switching devices on a private network to locate voice users' addresses and process other services. PBXs also allow users on the private network to access the IMS or PSTN through SIP trunks. -SIP AGs provide only the second function of PBXs. SIP AGs can be considered to be a plain old telephone service (POTS) that can register with the IMS using SIP trunks. PBXs use SIP trunks to register with other SIP servers. SIP AGs register with the IMS using POTS user numbers. PBXs and SIP AGs provides the same services. However, PBXs provide the services by themselves.

Differences between the AG and PBX
The differences between the access gateway (AG) and PBX are as follows: - A PBX can function as the switching layer device of the private network and provides address positioning and other services for voice users. It can also connect private network users to the IMS or PSTN through trunks such as SIP trunks. - An AG refers to a media access gateway. Compared with the PBX, the AG can only connect private network users to the IMS or PSTN through trunks such as SIP trunks. - The SIP AG is based on SIP. - The H248 AG is based on H248.

Is the user name mandatory when I configure SIP user registration on the IAD?
On the UC2.0 network, you must configure the user name (in domain name format) when configuring SIP user registration on the IAD. On other networks, you do not need to configure the user name. You only need to enter the user ID and corresponding authentication password.

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