Configuring gateway preferred forking

Owned by Balázs Oláh
Feb 01, 2016
1 min read

Gateway requirements

  • Supports both Voice gateways and Unified Border Elements (CUBE) as long as they interface with Unified CM using SIP and the Router platform supports the UC Services Interface (not supported for H323 or MGCP based calls)
  • The word gateway is used interchangeably to refer to both Voice gateways and CUBE devices.
  • The Gateway has to be directly connected to the Unified CM using a SIP trunk. No support for SIP Proxy servers
  • ISR-G2 Gateways (29XX, 39XX Series) running release 15.3(3)M or later are supported. 15.3(3)M was released on CCO in July / 2013
  • ASR-100X Gateways running release XE 3.10 or later are supported. XE 3.10 was released on CCO in July / 2013
  • VG224 is not currently supported

Configuring the Cisco UCM

You need to mark the Gateway - CUCM trunk as recording enabled:

Follow the Configuring Cisco UCM for central recording guide to create them.

Configuring the Cisco gateway

Create xmf provider using the following commands to each CUCM subscriber node: (replace the example ip address to your Cisco UCM ip address(es))

Device# configure terminal
Device(config)# uc wsapi
Device(config-uc-wsapi)# provider xmf
Device(config-uc-wsapi)# no shutdown
Device(config-uc-wsapi)# remote-url 1 http://192.168.111.111:8090/ucm_xmf
Device(config-uc-wsapi)# end
Device# show wsapi registration all

Provider XCC
=====================================================

Provider XMF
=====================================================
registration index: 1
id: 32EC5A98:XMF:Unified CM 10.5.0.99833-3:4
appUrl:http://192.168.111.111:8090/ucm_xmf
appName: Unified CM 10.5.0.99833-3
provUrl: http://192.168.111.111:8090/xmf
prober state: STEADY
connEventsFilter: CREATED|DISCONNECTED
mediaEventsFilter:

Â