Abstract: Emergency calls that use real time text (RTT) in addition to audio face a challenge: between an originating endpoint (e.g., a cellular network) sending a session initiation protocol (SIP) invite and receiving the response (e.g., 200 OK) from a downstream terminating endpoint (e.g., a peering network), the media attribute fields associated with the text and audio data may become swapped. Three options are disclosed for dealing with this issue. (1) The originating endpoint may swap the protocol paths for the RTT and audio data so that the public safety answering point (PSAP) and the user equipment (UE) are able to communicate. (2) The originating endpoint may send a correction request to the terminating endpoint. (3) If default protocol paths are specified for RTT and audio, the originating endpoint uses the default protocol paths independently of whether the SIP invite or response specified the correct data type and protocol path association.

Abstract: Solutions for temporary emergency call-back allowance over wireless networks improve public safety. A user equipment (UE), associated with a suspended post-paid subscriber account, places an emergency call, such as e911 or e112, over a wireless network (e.g., cellular), and the network flags the subscriber account associated with the UE as permitted to receive incoming calls for some time period, such as 5 to 30 minutes. This permits the UE to receive calls from the public safety answering point (PSAP), in the event that the call is prematurely disconnected, or the PSAP has a need to call the UE back to obtain additional information. In some examples, the UE suspends call blocking, in order to preclude the possibility of inadvertently blocking an incoming call from the PSAP. In some examples, the network sends a call-back policy to the UE identifying the duration of suspending call blocking and/or receiving incoming calls.