Table Of Contents
D
ddr timeout
directory exchange endpoint request
directory exchange messaging-gateway request
directory exchange messaging-gateway send
D
Last Updated: November 17, 2010
ddr timeout
directory exchange endpoint request
directory exchange messaging-gateway request
directory exchange messaging-gateway send
ddr timeout
To configure a timeout window whose elapse will result in a delayed delivery receipt (DDR), use the ddr timeout command in Cisco UMG configuration mode.
DDR timeout 0-24
Syntax Description
timeout 0-24
|
This is a numeric value in hours. Range: 0-24 hours.
|
Command Default
One hour
Command Modes
Cisco UMG configuration (config)
Command History
Cisco UMG Version
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Use this command to change the default settings. The range of acceptable values is 0 to 24 hours.
Examples
The following example sets a DDR timeout:
umg# config t
umg-1(config)# DDR timeout 2
umg# show DDR timeout
Timeout window for DDR is 2 hours
Related Commands
Command
|
Description
|
ndr timeout
|
Configures a timeout window for non-delivery receipts.
|
show ddr timeout
|
Displays the timeout window for DDRs.
|
directory exchange endpoint request
To manually force data convergence between autoregistered endpoints and messaging gateways, through either full directory exchange or directory updates, specifying that the action apply to a single location or to all locations, use the directory exchange endpoint request command in Cisco UMG EXEC mode.
directory exchange endpoint request { full [ location-id ] | update [ location-id ] }
Syntax Description
full [ location-id ]
|
Requests a full directory exchange (as opposed to the partial exchange which is an update) from the endpoint specified by the location ID. The range is 1 to 10 digits.
|
update [ location-id ]
|
Requests a partial directory exchange (only what has changed since the last directory exchange) from the endpoint specified by the location ID. The range is 1 to 10 digits.
|
Command Modes
Cisco UMG EXEC
Command History
Cisco UMG Version
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Use this command when you think that the current configuring messaging gateway might not have successfully exchanged directories or updates with one or more autoregistered endpoints.
Under normal circumstances, any changes to endpoint configuration (such as deletion) automatically triggers directory exchange.
Examples
In this example, the current configuring messaging gateway pulls an update from all endpoints, decides that endpoint 41000 should exchange its full directory, then the current configuring messaging gateway pulls full updates from all peer messaging gateways, and finally sends an update to messaging gateway 70707.
umg-1# directory exchange endpoint request update
umg-1# directory exchange endpoint request full 41000
umg-1# directory exchange messaging-gateway request full
umg-1# directory exchange messaging-gateway send update 70707
Related Commands
directory exchange messaging-gateway request
To manually force data convergence between the current messaging gateway and its peers by sending a request for either full directory exchange or directory updates, specifying that the action apply to a single location or to all locations, use the directory exchange messaging-gateway request command in Cisco UMG EXEC mode.
directory exchange messaging-gateway request { full [ location-id ] | update [ location-id ] }
Syntax Description
full [ location-id ]
|
Requests a full directory exchange (as opposed to the partial exchange which is an update) from the messaging gateway specified by the location ID. The range is 1 to 10 digits.
|
update [ location-id ]
|
Requests a partial directory exchange (only what has changed since the last directory exchange) from the messaging gateway specified by the location ID. The range is 1 to 10 digits.
|
Command Modes
Cisco UMG EXEC
Command History
Cisco UMG Version
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Use this command when you think that the current configuring messaging gateway might be out of synch with its peers.
Under normal circumstances, any changes to endpoint configuration (such as deletion) automatically triggers directory exchange between peers.
Examples
In this example, the current configuring messaging gateway pulls an update from all endpoints, decides that endpoint 41000 should exchange its full directory, then the current configuring messaging gateway pulls full updates from all peer messaging gateways, and finally sends an update to messaging gateway 70707.
umg-1# directory exchange endpoint request update
umg-1# directory exchange endpoint request full 41000
umg-1# directory exchange messaging-gateway request full
umg-1# directory exchange messaging-gateway send update 70707
Related Commands
directory exchange messaging-gateway send
To manually force data convergence between the current messaging gateway and its peers, by sending either full directory exchange or directory updates from the current configuring Cisco UMG, to a single location or to all locations, use the directory exchange messaging-gateway send command in Cisco UMG EXEC mode.
directory exchange messaging-gateway send {full [location-id] | update [location-id]}
Syntax Description
full [ location-id ]
|
Sends a full directory exchange (as opposed to the partial exchange which is an update) to peer messaging gateway(s).
|
update [ location-id ]
|
Sends a partial directory exchange (only what has changed since the last directory exchange) to peer messaging gateway(s).
|
Command Modes
Cisco UMG EXEC
Command History
Cisco UMG Version
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Use this command when you have reason to think that the current configuring messaging gateway might not have successfully exchanged directories or updates with one or more peers.
Under normal circumstances, any changes to endpoint configuration (such as deletion) will automatically trigger directory exchange.
Examples
In this example, the current configuring messaging gateway pulls an update from all endpoints, decides that endpoint 41000 should exchange its full directory, then the current configuring messaging gateway pulls full updates from all peer messaging gateways, and finally sends an update to gateway 70707.
umg-1# directory exchange endpoint request update
umg-1# directory exchange endpoint request full 41000
umg-1# directory exchange messaging-gateway request full
umg-1# directory exchange messaging-gateway send update 70707
Related Commands