No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

Quidway router connected to some other company's router(Hereinafter we call it RouterC) on VOFR protocol fails to intercommunicate for fragment configuration

Publication Date:  2012-07-27  |   Views:  146  |   Downloads:  0  |   Author:  Pei Dapeng  |   Document ID:  EKB0000008802


Issue Description

Version Info: Quidway R3640E: VRP (tm) software, Version 1.60 8040-001, Bootrom Version is 4.33. Description of Fault: RouterC is configured "vofr data 5 call-control 4", but it will not appear when you SHOW RUNNING CONFIGURATION. By the time, the telephone can call from one side to another, and the Serial0 interfaces cannot ping from one side to another. If "vofr data 5 call-control 4" is canceled, then the Serial0 interfaces can ping from one side to another, and the telephone cannot call from one side to another. This moment we capture the debug info while calling from Quidway side. At RouterC side there is no debug info. The result is that there isn't any voice after finishing a dial-up. When it comes to start a call from RouterC side, busy tone appears.

Alarm Information


Handling Process

Add fragment configuration on both sides. Configure "Frame-Relay Fragment" in "Map-Class frame?Relay Vofr". For example: map-class frame-relay vofr frame-relay voice bandwidth 32000 frame-relay fragment 1600 data-level In the real test, this problem is solved after finish the change.

Root Cause

Absence of fragment configuration gives cause for this problem. Quidway router runs mult-protocol encapsulation for none-voice data while RouterC runs FRF11 encapsulation. So they cannot intercommunicate.