https://docs.telcobridges.com/w/api.php?action=feedcontributions&feedformat=atom&user=Marc-Andre+Joyal 2026-07-27T19:07:21Z User contributions MediaWiki 1.41.1 https://docs.telcobridges.com/w/index.php?title=SIP_Emergency&diff=29067 2020-10-30T00:51:14Z

<p>Marc-Andre Joyal: </p> <hr /> <div><br /> <br /> == SIP Emergency ==<br /> <br /> The SIP Emergency Call Handling allow for the identification of emergency SIP calls and their reservation of licensed resources.<br /> <br /> SIP Emergency Call Handling configuration contains a list of rules to verify against when receiving a SIP Invite message. Each rule contains a condition. During establishment of a SIP session each rule are tested. When one rule matches the remaining rules are skipped. When a SIP session matches the condition of a SIP Emergency call handling rule, the SIP session is flagged as an emergency call and reserved resources are allocated to the session.<br /> <br /> == SIP Emergency Call Legs Reserved ==<br /> <br /> The Call Legs Reserved parameter specify the number of SIP UA call legs reserved for emergency calls and cannot be used for normal calls. There is 2 SIP UA call legs per SIP session. Must be inferior to the license total SIP UA call legs. However, emergency calls can go over 'Calls Legs Reserved' as long as there are unused SIP UA call legs left in the license.<br /> <br /> == SIP Emergency Inbound Rules ==<br /> <br /> A SIP Emergency Call Handling Inbound Rules consist of 3 parameters, Name, Header Containing the Service, and Identifier of Service.<br /> <br /> == Header Containing the Service ==<br /> <br /> This parameter indicates for a given rule the SIP header that should be used to try to match a SIP Emergency Call.<br /> <br /> Here is the list of supported Header Types:<br /> <br /> *'''Request-URI'''<br /> *'''To-URI'''<br /> *'''Resource-Priority'''<br /> *'''P-Asserted-ID'''<br /> *'''Priority'''<br /> <br /> == Identifier of Service ==<br /> <br /> This parameter indicates for a given rule the value that should be present in the header identified by 'Header Containing the Service' to match the rule.<br /> <br /> == Configuration ==<br /> <br /> *[[Toolpack:Tsbc_Protocol_Stack_Settings_3.1|v3.1: SIP Emergency]]<br /> <br /> == Example configuration ==<br /> In this configuration 40 call legs are reserved for SIP Emergency call Handling and a rule is configured using the P_Asserted_Identity header. &lt;br\&gt;<br /> [[File:SIP_Emergency.png|900px|SIP_Emergency.png]] &lt;br\&gt;<br /> &lt;br\&gt;<br /> Here a SIP Emergency Inbound Rule is being edited. It shows the selected header and the token the header in the SIP Invite should contains to match the rule. &lt;br\&gt;<br /> [[File:SIP_Emergency_rule.png|900px|SIP_Emergency_rule.png]] &lt;br\&gt;<br /> &lt;br\&gt;<br /> <br /> <br /> [[category:Glossary]]<br /> [[Category:Revise on Major]]</div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=SIP_Emergency&diff=29066 2020-10-30T00:50:14Z

<p>Marc-Andre Joyal: </p> <hr /> <div><br /> <br /> == SIP Emergency ==<br /> <br /> The SIP Emergency Call Handling allow for the identification of emergency SIP calls and their reservation of licensed resources.<br /> <br /> SIP Emergency Call Handling configuration contains a list of rules to verify against when receiving a SIP Invite message. Each rule contains a condition. During establishment of a SIP session each rule are tested. When one rule matches the remaining rules are skipped. When a SIP session matches the condition of a SIP Emergency call handling rule, the SIP session is flagged as an emergency call and reserved resources are allocated to the session.<br /> <br /> == SIP Emergency Call Legs Reserved ==<br /> <br /> The Call Legs Reserved parameter specify the number of SIP UA call legs reserved for emergency calls and cannot be used for normal calls. There is 2 SIP UA call legs per SIP session. Must be inferior to the license total SIP UA call legs. However, emergency calls can go over 'Calls Legs Reserved' as long as there are unused SIP UA call legs left in the license.<br /> <br /> == SIP Emergency Inbound Rules ==<br /> <br /> A SIP Emergency Call Handling Inbound Rules consist of 3 parameters, Name, Header Containing the Service, and Identifier of Service.<br /> <br /> == Header Containing the Service ==<br /> <br /> This parameter indicates for a given rule the SIP header that should be used to try to match a SIP Emergency Call.<br /> <br /> Here is the list of supported Header Types:<br /> <br /> *'''Request-URI'''<br /> *'''To-URI'''<br /> *'''Resource-Priority'''<br /> *'''P-Asserted-ID'''<br /> *'''Priority'''<br /> <br /> == Identifier of Service ==<br /> <br /> This parameter indicates for a given rule the value that should be present in the header identified by 'Header Containing the Service' to match the rule.<br /> <br /> == Configuration ==<br /> <br /> *[[Toolpack:Tsbc_Protocol_Stack_Settings_3.1|v3.1: SIP Emergency]]<br /> <br /> == Example configuration ==<br /> In this configuration 40 call legs are reserved for SIP Emergency call Handling and a rule is configured using the P_Asserted_Identity header. &lt;br\&gt;<br /> [[File:SIP_Emergency.png|900px|SIP_Emergency.png]] &lt;br\&gt;<br /> &lt;br\&gt;<br /> Here a SIP Emergency Inbound Rule is being edited. It shows the selected header and the value the header in the SIP Invite should contains to match the rule. &lt;br\&gt;<br /> [[File:SIP_Emergency_rule.png|900px|SIP_Emergency_rule.png]] &lt;br\&gt;<br /> &lt;br\&gt;<br /> <br /> <br /> [[category:Glossary]]<br /> [[Category:Revise on Major]]</div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=File:SIP_Emergency_rule.png&diff=29065 2020-10-30T00:46:28Z

<p>Marc-Andre Joyal: </p> <hr /> <div></div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=SIP_Emergency&diff=29064 2020-10-30T00:44:41Z

<p>Marc-Andre Joyal: </p> <hr /> <div><br /> <br /> == SIP Emergency ==<br /> <br /> The SIP Emergency Call Handling allow for the identification of emergency SIP calls and their reservation of licensed resources.<br /> <br /> SIP Emergency Call Handling configuration contains a list of rules to verify against when receiving a SIP Invite message. Each rule contains a condition. During establishment of a SIP session each rule are tested. When one rule matches the remaining rules are skipped. When a SIP session matches the condition of a SIP Emergency call handling rule, the SIP session is flagged as an emergency call and reserved resources are allocated to the session.<br /> <br /> == SIP Emergency Call Legs Reserved ==<br /> <br /> The Call Legs Reserved parameter specify the number of SIP UA call legs reserved for emergency calls and cannot be used for normal calls. There is 2 SIP UA call legs per SIP session. Must be inferior to the license total SIP UA call legs. However, emergency calls can go over 'Calls Legs Reserved' as long as there are unused SIP UA call legs left in the license.<br /> <br /> == SIP Emergency Inbound Rules ==<br /> <br /> A SIP Emergency Call Handling Inbound Rules consist of 3 parameters, Name, Header Containing the Service, and Identifier of Service.<br /> <br /> == Header Containing the Service ==<br /> <br /> This parameter indicates for a given rule the SIP header that should be used to try to match a SIP Emergency Call.<br /> <br /> Here is the list of supported Header Types:<br /> <br /> *'''Request-URI'''<br /> *'''To-URI'''<br /> *'''Resource-Priority'''<br /> *'''P-Asserted-ID'''<br /> *'''Priority'''<br /> <br /> == Identifier of Service ==<br /> <br /> This parameter indicates for a given rule the value that should be present in the header identified by 'Header Containing the Service' to match the rule.<br /> <br /> == Configuration ==<br /> <br /> *[[Toolpack:Tsbc_Protocol_Stack_Settings_3.1|v3.1: SIP Emergency]]<br /> <br /> == Example configuration ==<br /> In this configuration 40 call legs are reserved for SIP Emergency call Handling and a rule is configured using the P_Asserted_Identity header. &lt;br\&gt;<br /> [[File:SIP_Emergency.png|900px|SIP_Emergency.png]] &lt;br\&gt;<br /> &lt;br\&gt;<br /> <br /> [[category:Glossary]]<br /> [[Category:Revise on Major]]</div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=File:SIP_Emergency.png&diff=29063 2020-10-30T00:42:00Z

<p>Marc-Andre Joyal: uploaded a new version of &amp;quot;File:SIP Emergency.png&amp;quot;</p> <hr /> <div>Example of SIP Emergency with 40 call legs reserved for SIP Emergency Call Handling and one configured rule using P_Asserted_Identity header.</div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=File:SIP_Emergency.png&diff=29062 2020-10-30T00:35:46Z

<p>Marc-Andre Joyal: Example of SIP Emergency with 40 call legs reserved for SIP Emergency Call Handling and one configured rule using P_Asserted_Identity header.</p> <hr /> <div>Example of SIP Emergency with 40 call legs reserved for SIP Emergency Call Handling and one configured rule using P_Asserted_Identity header.</div>

Marc-Andre Joyal https://docs.telcobridges.com/w/index.php?title=SIP_Emergency&diff=29061 2020-10-29T21:20:01Z

<p>Marc-Andre Joyal: Created page with &quot; == SIP Emergency == The SIP Emergency Call Handling allow for the identification of emergency SIP calls and their reservation of licensed resources. SIP Emergency Call Han...&quot;</p> <hr /> <div><br /> <br /> == SIP Emergency ==<br /> <br /> The SIP Emergency Call Handling allow for the identification of emergency SIP calls and their reservation of licensed resources.<br /> <br /> SIP Emergency Call Handling configuration contains a list of rules to verify against when receiving a SIP Invite message. Each rule contains a condition. During establishment of a SIP session each rule are tested. When one rule matches the remaining rules are skipped. When a SIP session matches the condition of a SIP Emergency call handling rule, the SIP session is flagged as an emergency call and reserved resources are allocated to the session.<br /> <br /> == SIP Emergency Call Legs Reserved ==<br /> <br /> The Call Legs Reserved parameter specify the number of SIP UA call legs reserved for emergency calls and cannot be used for normal calls. There is 2 SIP UA call legs per SIP session. Must be inferior to the license total SIP UA call legs. However, emergency calls can go over 'Calls Legs Reserved' as long as there are unused SIP UA call legs left in the license.<br /> <br /> == SIP Emergency Inbound Rules ==<br /> <br /> A SIP Emergency Call Handling Inbound Rules consist of 3 parameters, Name, Header Containing the Service, and Identifier of Service.<br /> <br /> == Header Containing the Service ==<br /> <br /> This parameter indicates for a given rule the SIP header that should be used to try to match a SIP Emergency Call.<br /> <br /> Here is the list of supported Header Types:<br /> <br /> *'''Request-URI'''<br /> *'''To-URI'''<br /> *'''Resource-Priority'''<br /> *'''P-Asserted-ID'''<br /> *'''Priority'''<br /> <br /> == Identifier of Service ==<br /> <br /> This parameter indicates for a given rule the value that should be present in the header identified by 'Header Containing the Service' to match the rule.<br /> <br /> == Configuration ==<br /> <br /> *[[Toolpack:Tsbc_Protocol_Stack_Settings_3.1|v3.1: SIP Emergency]]<br /> <br /> == Example configuration ==<br /> <br /> [[category:Glossary]]<br /> [[Category:Revise on Major]]</div>

Marc-Andre Joyal