When emergency calls (for example, calls to 911) are received, the SBC Core recognizes them and proceeds to route them directly without any check for provisioned services. For proper routing to occur, an emergency routing label, emergency routes, and an emergency standard route entity must be provisioned.
The SBC supports configuring up to 32 emergency number prefixes and up to 10 service URNs in an Emergency Call Profile. If an incoming SIP INVITE has a R-URI with a prefix that matches one of the configured prefixes, or the R-URI contains a service URN configured in the urnPrefix table, the SBC treats the INVITE as an emergency session establishment.
% set profiles services emergencyCallProfile <profile name> cpc <none | priority> prefix <prefix> resPriorityHeaderProfile <profile name> sosInContactOfRegister <disable | enable> urnPrefix <prefix> xemg <disabled | enabled>
The Emergency Call Profile Parameters are as shown:
The following example creates an Emergency Call Profile named "EmergCall-1", and specifies to use 'cpc=priority' as emergency call indicator. Also, "911" is set as an Emergency prefix so that any incoming call with a prefix of "911" is classified as an emergency call. The flag sosInContactOfRegister
is enabled as well.
% set profiles services emergencyCallProfile EmergCall-1 cpc priority prefix 911 resPriorityHeaderProfile RPHProfile sosInContactOfRegister enable % show profiles services emergencyCallProfile emergencyCallProfile EmergCall-1 { prefix 911; cpc priority; resPriorityHeaderProfile RPHProfile; sosInContactOfRegister enable; }