• Supported Platforms
• M10i Routers, M120 Routers, M320 Routers, M7i Routers
• MX240 Routers, MX480 Routers, MX960 Routers
• T640 Routers

• Related Topics
• For a description of PGCP statements, see Summary of PGCP Configuration Statements in Junos Services Interfaces Configuration Guide
• For a description of the fields in show commands, see PGCP Operational Mode Commands for the BGF Feature in Junos System Basics and Services Command Reference

Example: Using the BGF to Provide VoIP Solutions in a Next-Generation Network

Requirements

This example uses the following software and hardware components:

• Junos OS Release 9.0 or later
• Juniper Networks T640 Core Router with a MultiServices 500 PIC

Overview and Topology

Table 1 shows the voice configuration components.

Configuration

• Configuring the SP BGF Router
• Configuring the Service Interfaces
• Configuring the Service Interface
• Configuring the Virtual BGFs
• Configuring NAT Pools
• Configuring the Virtual Interfaces
• Configuring Rules for the BGF
• Configuring a Stateful Firewall
• Configuring a Service Set
• Configuring QoS for Voice Calls

Configuring the SP BGF Router

CLI Quick Configuration

Configuring the Service Interfaces

CLI Quick Configuration

To quickly configure the service interfaces, copy the following commands and paste them into the router terminal window:

Configuring the Service Interface

Step-by-Step Procedure

To configure the service interface:

1. Create the interface, and enter edit mode for the interface.
   [edit interfaces]user@sp-bgf-router# edit sp-1/2/0
2. Configure an IPv4 service interface for bgf-1 and bgf-2.
   [edit interfaces sp-1/2/0]user@sp-bgf-router# set description bgf1_bgf2_pgcp_service_ipv4user@sp-bgf-router# set unit 0 family inetuser@sp-bgf-router# set unit 10 family inetuser@sp-bgf-router# set unit 20 family inetuser@sp-bgf-router# set unit 30 family inetuser@sp-bgf-router# set unit 40 family inetuser@sp-bgf-router# set traceoptions flag alluser@sp-bgf-router# set services-options syslog host local services any
3. Configure an IPv6 service interface for bgf-3.
   [edit interfaces sp-1/2/1]user@sp-bgf-router# set sp-1/2/1 description bgf3_pgcp_service_ipv6user@sp-bgf-router# set sp-1/2/1 unit 0 family inet6user@sp-bgf-router# set sp-1/2/1 unit 10 family inet6user@sp-bgf-router# set sp-1/2/1 unit 20 family inet6user@sp-bgf-router# set sp-1/2/1 traceoptions flag alluser@sp-bgf-router# set sp-1/2/1 services-options syslog host local services any

Results

Display the results of the configuration.

Configuring the Virtual BGFs

CLI Quick Configuration

To quickly configure the virtual BGFs, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To configure the virtual BGFs:

1. Configure BGF-1.
   [edit services pgcp]user@sp-bgf-router# edit gateway bgf-1 [edit services pgcp gateway bgf-1]user@sp-bgf-router# set gateway-address 172.16.10.1user@sp-bgf-router# set gateway-port 2944user@sp-bgf-router# set cleanup-timeout 3600user@sp-bgf-router# set gateway-controller gc-1 controller-address 33.0.0.1user@sp-bgf-router# set gateway-controller gc-1 controller-port 2944user@sp-bgf-router# set gateway-controller gc-1 interim-ah-scheme algorithm hmac-null
2. Configure BGF-2.
   [edit services pgcp]user@sp-bgf-router# edit gateway bgf-2 [edit services pgcp gateway bgf-2]user@sp-bgf-router# set gateway-address 172.16.20.2user@sp-bgf-router# set gateway-port 2944user@sp-bgf-router# set cleanup-timeout 3600user@sp-bgf-router# set gateway-controller gc-1 controller-address 33.0.0.1user@sp-bgf-router# set gateway-controller gc-1 controller-port 2944user@sp-bgf-router# set gateway-controller gc-1 interim-ah-scheme algorithm hmac-null
3. Configure BGF-3.
   [edit services pgcp]user@sp-bgf-router# edit gateway bgf-3 [edit services pgcp gateway bgf-3]user@sp-bgf-router# set gateway-address 172.16.30.3user@sp-bgf-router# set gateway-port 2944user@sp-bgf-router# set cleanup-timeout 3600user@sp-bgf-router# set gateway-controller gc-1 controller-address 33.0.0.1user@sp-bgf-router# set gateway-controller gc-1 controller-port 2944user@sp-bgf-router# set gateway-controller gc-1 interim-ah-scheme algorithm hmac-null

Configuring NAT Pools

CLI Quick Configuration

To quickly configure the NAT pools, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To configure NAT pools:

1. Create a media (RTP) NAT pool for BGF-1 for the access (peering) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf1_peer_rtp-nat-pool-1 [edit services nat pool bgf1_peer_rtp-nat-pool-1]user@sp-bgf-router# set address 11.0.0.5user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set pool pg1_peer_rtp-nat-pool-1 pgcp ports-per-session 2
2. Create a media (RTP) NAT pool for BGF-2 for the access (peering) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf2_peer_rtp-nat-pool-2[edit services nat pool bgf2_peer_rtp-nat-pool-2]user@sp-bgf-router# set address 11.0.0.25user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp ports-per-session 2
3. Create a media (RTP) NAT pool for BGF-3 for the access (peering) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf3_peer_rtp-nat-pool-3[edit services nat pool bgf3_peer_rtp-nat-pool-3]user@sp-bgf-router# set address 2001:db8:10:3::100/128user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp ports-per-session 2
4. Create a media (RTP) NAT pool for BGF-1 for the backbone (service provider) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf1_core_rtp-nat-pool-4 [edit services nat pool bgf1_core_rtp-nat-pool-4]user@sp-bgf-router# set address 10.0.0.5user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp ports-per-session 2
5. Create a media (RTP) NAT pool for BGF-2 for the backbone (service provider) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf2_core_rtp-nat-pool-5[edit services nat pool bgf2_core_rtp-nat-pool-5]user@sp-bgf-router# set address 10.0.0.25user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set ports-per-session 4
6. Create a media (RTP) NAT pool for BGF-3 for the backbone (service provider) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf3_core_rtp-nat-pool-6[edit services nat pool bgf3_core_rtp-nat-pool-6]user@sp-bgf-router# set address 2001:db8:13:2::100/128user@sp-bgf-router# set port automaticuser@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp ports-per-session 2
7. Configure a signaling (SIP) NAT pool for BGF-1 for the access (peering) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool vgp1_peer_sip-nat-pool-7 [edit services nat pool vgp1_peer_sip-nat-pool-7]user@sp-bgf-router# set address 11.0.0.2user@sp-bgf-router# set port range low 10000 high 50000user@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp remotely-controlleduser@sp-bgf-router# set ports-per-session 2
8. Configure a signaling (SIP) NAT pool for the backbone (service provider) side of the network.
   [edit services nat]user@sp-bgf-router# edit pool bgf1_core_sip-nat-pool-8[edit services nat pool bgf1_core_sip-nat-pool-8]user@sp-bgf-router# set address 10.0.0.2user@sp-bgf-router# set port range low 10000 high 50000user@sp-bgf-router# set pgcpuser@sp-bgf-router# set pgcp remotely-controlleduser@sp-bgf-router# set pgcp ports-per-session 2

Results

Display the results of the configuration:

Configuring the Virtual Interfaces

CLI Quick Configuration

To quickly configure the virtual interfaces, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To configure a virtual interface:

1. Create a virtual interface for the backbone (service provider) side of the network. Specify the names of the NAT pools to be used for gates on the virtual interface that you are configuring.
   [edit services pgcp]edit virtual-interface 1[edit services pgcp virtual-interface 1]user@sp-bgf-router# set nat-pool bgf1_core_rtp_nat-pool-4user@sp-bgf-router# set nat-pool bgf1_core_sip_nat-pool-8user@sp-bgf-router# set nat-pool bgf2_core_rtp_nat-pool-5user@sp-bgf-router# set nat-pool bgf3_core_rtp_nat-pool-6
2. Create a virtual interface for the access (peering) side of the network. Specify the names of the NAT pools to be used for gates on the virtual interface that you are configuring.
   [edit services pgcp]edit virtual-interface 2[edit services pgcp virtual-interface 2]user@sp-bgf-router# set nat-pool bgf1_peer_rtp_nat-pool-1user@sp-bgf-router# set nat-pool bgf1_peer_sip_nat-pool-7user@sp-bgf-router# set nat-pool bgf2_peer_rtp_nat-pool-2user@sp-bgf-router# set nat-pool bgf3_peer_rtp_nat-pool-3

Results

Display the results of the configuration.

Configuring Rules for the BGF

CLI Quick Configuration

To quickly define the rules, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To configure the rules for the BGF:

1. Create a rule for bgf-1, and the NAT pools to be used for this virtual BGF.
   [edit services pgcp]user@sp-bgf-router# edit rule bgf-rule1[edit services pgcp rule bgf-rule1]user@sp-bgf-router# set gateway bgf-1 user@sp-bgf-router# set nat-pool bgf1_peer_rtp_nat-pool-1user@sp-bgf-router# set nat-pool bgf1_peer_sip_nat-pool-7user@sp-bgf-router# set nat-pool bgf1_core_rtp_nat-pool-4 user@sp-bgf-router# set nat-pool bgf1_core_sip_nat-pool-8
2. Create a rule for bgf-2, and specify the NAT pools to be used for this virtual BGF.
   [edit services pgcp]user@sp-bgf-router# edit rule bgf-rule2[edit services pgcp rule bgf-rule2]user@sp-bgf-router# set gateway bgf-2user@sp-bgf-router# set nat-pool bgf2_peer_rtp_nat-pool-2user@sp-bgf-router# set nat-pool bgf2_core_rtp_nat-pool5
3. Create a rule for bgf-3, and specify the NAT pools to be used for this virtual BGF.
   [edit services pgcp]user@sp-bgf-router# edit rule bgf-rule3[edit services pgcp rule bgf-rule3]user@sp-bgf-router# set gateway bgf-3set rule bgf-rule3 gateway bgf-3 nat-pool bgf3_peer_rtp_nat-pool-3set rule bgf-rule3 gateway bgf-3 nat-pool bgf3_core_rtp_nat-pool-6

Results

Display the results of the configuration.

Configuring a Stateful Firewall

CLI Quick Configuration

To quickly define the rules, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To create a stateful firewall:

1. Create a stateful firewall rule.
   [edit services stateful-firewall]user@host# edit rule r1
2. Set the match direction for the rule.
   [edit services stateful-firewall rule r1]user@host# set match-direction input-output
3. Add a term to the rule with the action set to reject.
   [edit services stateful-firewall rule r1]user@host# set term t1 then reject

Results

Display the results of the configuration.

Configuring a Service Set

CLI Quick Configuration

To quickly define a service set, copy the following commands and paste them into the router terminal window:

Step-by-Step Procedure

To configure the service sets:

1. Configure a service set for bgf-1.
   [edit services]user@sp-bgf-router# edit service-set bgf1-svc-set
   [edit services service-set bgf1-svc-set]user@sp-bgf-router# set pgcp-rules bgf-rule1user@sp-bgf-router# set stateful-firewall-rules r1 user@sp-bgf-router# set next-hop-service service-interface-pool int-pool–1 user@sp-bgf-router# set syslog host local-1 services any
2. Configure a service set for BGF-2.
   [edit services]user@sp-bgf-router# edit service-set bgf2-svc-set [edit services service-set bgf2-svc-set]user@sp-bgf-router# set pgcp-rules bgf-rule2user@sp-bgf-router# set stateful-firewall-rules r1 user@sp-bgf-router# set next-hop-service service-interface-pool int-pool–2user@sp-bgf-router# set syslog host local-1 services any
3. Configure a service set for BGF-3.
   [edit services]user@sp-bgf-router# edit service-set bgf3-svc-set [edit services service-set bgf3-svc-set]user@sp-bgf-router# set pgcp-rules bgf-rule3user@sp-bgf-router# set stateful-firewall-rules r1 user@sp-bgf-router# set next-hop-service service-interface-pool int-pool–3 user@sp-bgf-router# set syslog host local-1 services any

Results

Configuring QoS for Voice Calls

CLI Quick Configuration

To quickly configure a default value for the Differentiated Services (DiffServ) code point (DSCP), copy the following command and paste it into the router terminal window:

Step-by-Step Procedure

To configure default values for H.248 DiffServ properties:

1. Access the configuration of the H.248 DiffServ properties.
   [edit services pgcp gateway bgf-1]user@sp-bgf-router# edit h248-properties diffserv
2. Configure a value for the DSCP.
   [edit services pgcp gateway bgf-1 h248-properties diffserv]user@sp-bgf-router# set dscp default 0x1D

Results

Display results of the configuration.

Verification

To confirm that the configuration is working properly, perform these tasks:

• Verifying the Active BGF Configuration
• Verifying That Gates Are Running
• Verifying Terminations
• Verifying PGCP Flows
• Verifying H.248 Parameters Set by the Gateway Controller

Verifying the Active BGF Configuration

Purpose

Verify the active BGF configuration that is running on your router.

Action

Packet gateway media service configuration:
 Media service name: bgf1_peer_rtp_ms1
  nat pool             :  bgf1_peer_rtp-nat-pool-1

Packet gateway media service configuration:
 Media service name: bgf2_peer_rtp_ms2
  nat pool             :  bgf2_peer_rtp-nat-pool-2

Packet gateway media service configuration:
 Media service name: bgf3_peer_rtp_ms3
  nat pool             :  bgf3_peer_rtp-nat-pool-3

Packet gateway media service configuration:
 Media service name: bgf1_core_rtp_ms4
  nat pool             :  bgf1_core_rtp-nat-pool-4

Packet gateway media service configuration:
 Media service name: bgf2_core_rtp_ms5
  nat pool             :  core_rtp-nat-pool-5

Packet gateway media service configuration:
 Media service name:  bgf3_core_rtp_ms6
  nat pool             :  bgf3_core_rtp-nat-pool-6

Packet gateway media service configuration:
 Media service name: bgf1_peer_sip_ms7
  nat pool             :  bgf1_peer_sip-nat-pool-7

Packet gateway media service configuration:
 Media service name: bgf1_core_sip_ms8
  nat pool             :  bgf1_core_sip-nat-pool-8

 Packet gateway virtual interface configuration:
  Virtual Interface name: 1
  Status               :  In-Service
  Media Service Name   :  bgf1_core_rtp_ms4
  Media Service Name   :  bgf1_core_sip_ms8
  Media Service Name   :  bgf2_core_rtp_ms5 
  Media Service Name   :  bgf2_core_rtp_ms5

 Packet gateway virtual interface configuration:
  Virtual Interface name: 2
  Status               :  In-Service
  Media Service Name   :  bgf1_peer_rtp_ms1
  Media Service Name   :  bgf1_peer_sip_ms7
  Media Service Name   :  bgf2_peer_rtp_ms2 
  Media Service Name   :  bgf3_peer_rtp_ms3

Virtual BGF configuration:
  Name                                     :  bgf-1
  IP address                               :  172.16.10.1
  Port                                     :  2944
  Status                                   :  In-Service (Registered)
  Active gateway controller                :  gc–1
  Replication socket                       :  Connected (Syncing)
  Cleanup timeout [secs]                   :  3600
  Gate inactivity delay [secs]             :  240
  Gate inactivity duration (Q-MI ) [secs]  :  86400
  Latching Deadlock duration [secs]        : 15

Virtual BGF configuration:
  Name                                     :  bgf-2
  IP address                               :  172.16.20.2
  Port                                     :  2944
  Status                                   :  In-Service (Disconnected)
  Active gateway controller                :    
  Replication socket                       :  Connected (Syncing)
  Cleanup timeout [secs]                   :  3600
  Gate inactivity delay [secs]             :  240
  Gate inactivity duration (Q-MI ) [secs]  :  86400
  Latching Deadlock duration [secs]        : 15

Virtual BGF configuration:
  Name                                     :  bgf-3
  IP address                               :  172.16.30.3
  Port                                     :  2944
  Status                                   :  In-Service (Disconnected)
  Active gateway controller                :  
  Replication socket                       :  Connected (Syncing)
  Cleanup timeout [secs]                   :  3600
  Gate inactivity delay [secs]             :  240
  Gate inactivity duration (Q-MI ) [secs]  :  86400
  Latching Deadlock duration [secs]        : 15

H248 timers configuration:
 Max waiting delay (MWD) [millisec]          :  10000
 Max retransmission delay (T-MAX) [millisec] :  25000
 Initial average ack delay (I-AAD) [millisec]:  1000
 Max net propagation delay (M-NPD) [millisec]:  5000

H248 options configuration:
 Wildcard response service-change        :  NO

H248 diffserv configuration:
 dscp          :  0x00

H248 segmentation        :               minimum        maximum        default
  MG segmentation timer [millisec]         :  500          30000          4000
  MG maximum PDU size [bytes]              :  512          65507          1472
  MGC segmentation timer [millisec]        :  500          30000          4000
  MGC maximum PDU size [bytes]             :  512          65507          1472

H248 base root           :                    minimum     maximum      default
  Normal MG execution time [millisec]      :  500           29000          500
  MG Provisional response timer [millisec] :  500           30000         2000
  MG Originated pending limit              :  1               512            4
  Normal MGC execution time [millisec]     :  500           29000          500
  MGC Provisional response timer [millisec]:  500           30000         4000
  MGC Originated pending limit             :  1               512            4

Fast update filters:
 Maximum terms              : 20000
 Maximum term percentage    : 10

Packet gateway controller configuration:
 Controller name                   :  gc-1
 Controller IP address             :  33.0.0.1
 Controller port                   :  2944

Packet gateway rule configuration:
 Rule name            :  bgf-rule1
 Gateway name         :  bgf-1

Packet gateway rule configuration:
 Rule name            :  bgf-rule2
 Gateway name         :  bgf-2

Packet gateway rule configuration:
 Rule name            :  bgf-rule3
 Gateway name         :  bgf-3

Packet gateway service set configuration:
 Service set name     :  bgf1-svc-set
 Service set id       :  1
 Rule name            :  bgf-rule1

Packet gateway service set configuration:
 Service set name     :  bgf2-svc-set
 Service set id       :  2
 Rule name            :  bgf-rule2

Packet gateway service set configuration:
 Service set name     :  bgf3-svc-set
 Service set id       :  3
 Rule name            :  bgf-rule3

Packet gateway service pics status:
 Name    : sp-1/2/0
 Status  : Connected

Packet gateway service pics status:
 Name    : sp-1/2/1
 Status  : Connected

Firewall:
 Status             :  Connected
 Number of terms    :  2
 Number of filters  :  2

Meaning

Use the show services pgcp active-configuration command to see your configuration and to display the current status of your virtual interfaces, virtual BGF, and services interfaces.

In addition, make sure that:

• At least one virtual BGF is In-Service (Registered). Virtual BGF Out-Of-Service might mean that:
  • The gateway controller is down.
  • The network connection between the gateway controller and the BGF is down, or there is a related network problem.
  • An unknown software problem exists. In this case, review the BGF logs for more information or contact JTAC.
• The replication socket is Connected. If it is not, graceful Routing Engine switchover (GRES ) is not enabled.
• The BGF service interface status is Connected. If it is not, there might be a hardware problem with the interface.
• The firewall status is Connected. If it is not, no connection exists to the fast update filters for rate limiting.

Verifying That Gates Are Running

Purpose

Verify that gates are running on bgf-1.

Action

Virtual BGF configuration:
  Name                                     :  bgf—1              
  IP address                               :  172.16.10.1           
  Port                                     :  2944              
  Status                                   :  In-Service (Registered) 

Gate information:
Gate id: 4295033088          
Gate state:  active 
Action: forward      
Service set id: 1     
Media card: sp-1/2/0                                                
Media handler: bgf1-svc-set                                          
Termination-id-string: ip/4/vif-0/2      

Gate id: 4295033089          
Gate state:  active 
Action: forward      
Service set id: 1     
Media card: sp-1/2/0                                                
Media handler: bgf1-svc-set                                          
Termination-id-string: ip/4/vif-0/3 

Meaning

The show services pgcp gates command lists the gates on the virtual BGF. It shows whether gates are active, disabled, or closed. It also shows the current action being performed on the gate: forward, add, or drop.

Verifying Terminations

Purpose

Verify the terminations on bgf-1.

Action

Virtual BGF configuration:
  Name                                     :  bgf–1              
  IP address                               :  172.16.10.1           
  Port                                     :  2944              
  Status                                   :  In-Service (Registered) 


Termination name                   State           Duration(msecs)         
ip/4/vif-0/2       In-service      390288          
Gate-id         Direction       State        Action
4295033088      A->B            active       forward      
4295033089      B->A            active       forward      


Termination name                   State           Duration(msecs)         
ip/4/vif-0/3       In-service      390294          
Gate-id         Direction       State        Action
4295033088      A->B            active       forward      
4295033089      B->A            active       forward      

Meaning

The show services pgcp terminations command lists the terminations on the virtual BGF. It shows whether the gates within a termination are active, disabled, or closed. You can use the termination names (termination IDs) to troubleshoot problems with voice calls.

Verifying PGCP Flows

Purpose

Verify the PGCP flows.

Action

Interface: sp-1/2/0, Service set: bgf1-svc-set
Flow                                                State    Dir       Frm count
Gate id: 4295033089          
UDP            20.0.0.1:0     ->    11.0.0.5:1024  Forward  I               0
    NAT source         20.0.0.1:0       ->     10.10.0.5:1024    
    NAT dest       11.0.0.5:1024    ->         10.0.0.1:20002   
Gate id: 4295033089          
UDP            20.0.0.1:0     ->    11.0.0.5:1025  Forward  I               0
    NAT source         20.0.0.1:0       ->     10.10.0.5:1025    
    NAT dest       11.0.0.5:1025    ->         10.0.0.1:20003   
Gate id: 4295033088          
UDP            0.0.0.0:0     ->    10.10.0.5:1024  Forward  I               0
    NAT source         0.0.0.0:0       ->     11.0.0.5:1024    
    NAT dest       10.10.0.5:1024    ->         20.0.0.1:10002   
Gate id: 4295033088          
UDP            0.0.0.0:0     ->    10.10.0.5:1025  Forward  I               0
    NAT source         0.0.0.0:0       ->     11.0.0.5:1025    
    NAT dest       10.10.0.5:1025    ->         20.0.0.1:10003   

Verifying H.248 Parameters Set by the Gateway Controller

Purpose

Verify the H.248 parameters that are set by the gateway controller.

Action

Termination information:
ip/4/vif-0/2 {
      MEDIA {
        TERMINATIONSTATE { SERVICESTATES = INSERVICE },
        STREAM = 1 {
          LOCALCONTROL { MODE = SENDRECEIVE,
                         DS/DSCP = 00,
                         TMAN/MBS = 0,
                         TMAN/PDR = 0,
                         TMAN/POL = OFF,
                         TMAN/SDR = 0,
                         MGCINFO/DB = 00,
                         GM/RSB = ON,
                         GM/SAF = OFF,
                         GM/SPF = OFF,
                         GM/SPR = 0,
                         GM/ESAS = OFF,
                         GM/ESPS = OFF,
                         GM/LSP = 0 },
          LOCAL {
v=0
c=IN IP4 10.10.0.5
m=- 1024 RTP/AVP -
b=AS:0
          },
          REMOTE {
v=0
c=IN IP4 10.0.0.1
m=- 20002 RTP/AVP -
b=AS:0
          }
        }
      },
      EVENTS = 1001 { NT/QUALERT { TH = 99, STREAM = 1 } },
      SIGNALS
    }

ip/4/vif-0/3 {
      MEDIA {
        TERMINATIONSTATE { SERVICESTATES = INSERVICE },
        STREAM = 1 {
          LOCALCONTROL { MODE = SENDRECEIVE,
                         DS/DSCP = 00,
                         TMAN/MBS = 1500,
                         TMAN/PDR = 0,
                         TMAN/POL = OFF,
                         TMAN/SDR = 125000,
                         MGCINFO/DB = 00,
                         GM/RSB = ON,
                         GM/SAF = ON,
                         GM/SAM = "[20.0.0.1]",
                         GM/SPF = OFF,
                         GM/SPR = 0,
                         GM/ESAS = OFF,
                         GM/ESPS = OFF,
                         GM/LSP = 0 },
          LOCAL {
v=0
c=IN IP4 11.0.0.5
m=- 1024 RTP/AVP -
b=AS:0
          },
          REMOTE {
v=0
c=IN IP4 4.0.0.1
m=- 10002 RTP/AVP -
b=AS:0
          }
        }
      },
      SIGNALS
    }
{master}

Meaning

The show services pgcp terminations gateway bgf-name h248 command presents the H.248 parameters as they have been set through H.248 requests and commands from the gateway controller. Comparing this output with the expected H.248 requests reveals whether there was a problem with the requests and commands that the gateway controller sent to the virtual BGF.

Troubleshooting

• No Audio is Reported on a Stream

No Audio is Reported on a Stream

Problem

A call completes correctly (signaling is completed), but the media (audio) stream expected to flow through the BGF fails.

Solution

Locate the failed terminations and gates.

1. Acquire the relevant gate IDs termination IDs using the show services pgcp gates command.
2. Display the H.248 parameters for the termination.
   
   

   user@sp-bgf-router> show services pgcp terminations gateway bgf-1 termination-prefix h248 ip/4/vif-0/2

   Termination information:
   ip/4/vif-0/2 {
         MEDIA {
           TERMINATIONSTATE { SERVICESTATES = INSERVICE },
           STREAM = 1 {
             LOCALCONTROL { MODE = SENDRECEIVE,
                            DS/DSCP = 00,
                            TMAN/MBS = 0,
                            TMAN/PDR = 0,
                            TMAN/POL = OFF,
                            TMAN/SDR = 0,
                            MGCINFO/DB = 00,
                            GM/RSB = ON,
                            GM/SAF = OFF,
                            GM/SPF = OFF,
                            GM/SPR = 0,
                            GM/ESAS = OFF,
                            GM/ESPS = OFF,
                            GM/LSP = 0 },
             LOCAL {
   v=0
   c=IN IP4 3.99.99.100
   m=- 1024 RTP/AVP -
   b=AS:0
             },
             REMOTE {
   v=0
   c=IN IP4 3.0.0.1
   m=- 20002 RTP/AVP -
   b=AS:0
             }
           }
         },
         EVENTS = 1001 { NT/QUALERT { TH = 99, STREAM = 1 } },
         SIGNALS
       }
   
   

3. Display information about the gate.
   
   

   user@sp-bgf-router> show services pgcp gate gateway gate-id 4295033088

   Gate information:
   Gate id: 4295033088          
   Gate state:  active 
   Action: forward      
   Service set id: 1     
   Media card: sp-1/2/0                                                
   Media handler: bgf1-svc-set                                          
   Termination-id-string: ip/4/vif-0/2      
    

Using the preceding information, review and verify the following:

1. Terminations are in the In-Service state.

   If the termination is in the Out-of-Service state, no streams are allowed access to the termination. The Out-of-Service state indicates a problem with either the resources on the BGF or incorrect parameters requested by the gateway controller.

2. The termination H.248 parameters are as expected.

   Pay special attention to the LOCAL and REMOTE parameters, and make sure they are aligned with the Session Description Protocol (SDP) offered by both elements participating in the session. Also, missing or unknown values suggest a problem with the call setup initiated by the gateway controller.

3. Gate actions are in the Forward state.

   If one or all gates are in the Drop state, no stream is allowed to flow through it, so one-way or no audio results. If a gate is not in the Forward state, the gateway controller might have failed to provide a required descriptor.

   Gate actions in the Forward state, but no media is flowing (frame count is zero or not advancing), can be caused by one of the following problems:

   • Networking or routing issues, including:
     • Stream fails to reach the router. A problem exists with the network path between the stream originator and the BGF gates.
     • Routing Engine, PIC, or DPC failure. The stream reaches the router, but the PIC or DPC fails to receive the stream. Use the show services pgcp active-configuration command to review the PIC or DPC status, and make sure that it is In-Service.
   • Hardware or element failure. The originator fails to send the stream. Use the debug tools available on the VoIP element to verify that the streams have left the element.
   • The originator is using a different source IP address than the one reported in the H.248 termination. Verify that the H.248 termination information matches the stream source and destination received by the BGF and the PIC or DPC. You can use the capture feature on the router to verify that the streams are received on the Packet Forwarding Engine.