Table Of Contents
Call Routing logic on Cisco UBE using the History-info Header
Configuring Call Routing Logic on Cisco UBE using the History-info Header Globally
Configuring all Routing Logic on Cisco UBE using the History-info Header at the Dial-Peer Level
Call Routing logic on Cisco UBE using the History-info Header
The history-info header has the call or dialog history information. The receiving application uses the history-info header information to determine how and why the call has reached it. SIP IOS GW does not utilize this information in History-Info header. The information stored in the History-Info headers can be used to bypass the dial-peers that were already tried during the course of a call, ensuring that the call is not being redirected again to the same target. The called-numbers and host portion of request URI in History-Info headers will be compared with the matching dial-peers, if incase the comparison succeeds, then those dial-peers will be bypassed.
This section contains the following procedures:
•Configuring Call Routing Logic on Cisco UBE using the History-info Header Globally
•Configuring all Routing Logic on Cisco UBE using the History-info Header at the Dial-Peer Level
Configuring Call Routing Logic on Cisco UBE using the History-info Header Globally
Perform this task to configure call routing on history-info header at a global level in SIP configuration (conf-serv-sip) mode.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice service voip
4. sip
5. call route history-info
6. exit
DETAILED STEPSConfiguring all Routing Logic on Cisco UBE using the History-info Header at the Dial-Peer Level
Perform this task to configure call routing on history-info header support at the dial-peer level, in dial peer voice configuration (config-dial-peer) mode.
SUMMARY STEPS
1. enable
2. configure terminal
3. dial-peer voice tag voip
4. voice-class sip call-route history-info
5. exit
DETAILED STEPS