Accessibilité Skip to content
Article ID: 000046706
Date de dernière modification: 12/08/2021
Access Level: Public
A call from an external CMAD client registered to the CMA via VBP-ST access proxy cannot connect to any systems registered to the DMA
The customer has installed the VBP-ST unit and is using the Access Proxy feature. An external CMAD client is able to register to the CMA via the VBP-ST Access Proxy function. The CMA is also neighbored to the customer’s DMA. A HDX and RMX have been added to the DMA. When the external CMAD client places a call to the HDX or RMX connected to the DMA, the call fails. The same external client can successfully call another CMAD client located on the internal network and vice versa. The internal CMAD client call the same HDX or RMX connected to the DMA. DMA logging set to DEBUG and CMA packet capture started. -- Internal CMAD 192.168.14.109 -- CMA 10.1.210.63 -- LAN VBP-ST 10.1.210.62 -- DMA VIP 10.1.210.66 In the CMA packet trace, the following is seen for H225 protocol: Failed Call: 1) No. 146 - LAN VBP-ST sends a ARQ to CMA -- Dial digits -> 701003 (70 is the DMA prefix and 1003 is a VMR) 2) No. 150 - CMA sends a LRQ to the DMA 3) No. 154 - the DMA responds with LCF 4) No. 155 - the CMA sends the VBP-ST an ACF 5) No. 253 - the DMA sends the CMA a DRQ 6) No. 254 - the CMA responds with a DCF The call ends soon after. Success call: 1) No. 353 The local CMAD client calls the CMA and sends an ARQ -- Dial digits -> 701003 (70 is the DMA prefix and 1003 is a VMR) 2) No. 355 CMA issues a LRQ to the DMA 3) No. 359 the DMA sends the CMA a LCF 4) No. 361 the CMA sends the internal CMAD an ACF The call completes.
Upgrade to VBP 11.2.10 or higher to resolve this issue.