A method, performed by a system comprising a user equipment, a content server, and an application server for switching a media session from multicast to unicast delivery, said media session being delivered from said content server to the user equipment via a multicast bearer of an IP network, wherein the following steps are performed: initiating (3:2), by the user equipment, a preparation phase, said preparation phase comprising requesting (3:3) said application server to prepare said content server for a switching from the multicast bearer to a unicast bearer; recognising (3:3), by the application server, a re-invite prepare message being received from the user equipment, said re-invite prepare message being a request for preparing said content server for said switch, but without negotiating any resources for any unicast bearer, wherein said-preparing comprises requesting said content server to prepare for said switch to a unicast bearer by initiating configuration of said ongoing multicast session for unicast delivery; recognising (3:7), by the application server, a response to said request from said content server; transmitting (3:8), by the application server, said response to said user equipment, said response comprising configuring data associated with said initiated configuration, the configuration data being associated with the unicast bearer preparation; receiving (3:9), by the user equipment, from said application server, the configuration data associated with said initiated configuration, the configuration data being associated with the unicast bearer preparation; and initiating, by the user equipment, a release phase, said release phase comprising releasing said multicast bearer, negotiating resources for a unicast bearer and subsequently requesting (3:14), via a trick play command comprising said configuration data, said content server to resume transmission of said media session via said unicast bearer, based on said configuration data, wherein said preparation phase and release phase are triggered by any of a splicing point in the received media stream, a timeout of timer, a trigger message, or a manual activation entered by a user of said user equipment. initiating (3:2), by the user equipment, a preparation phase, said preparation phase comprising requesting (3:3) said application server to prepare said content server for a switching from the multicast bearer to a unicast bearer; recognising (3:3), by the application server, a re-invite prepare message being received from the user equipment, said re-invite prepare message being a request for preparing said content server for said switch, but without negotiating any resources for any unicast bearer, wherein said-preparing comprises requesting said content server to prepare for said switch to a unicast bearer by initiating configuration of said ongoing multicast session for unicast delivery; recognising (3:7), by the application server, a response to said request from said content server; transmitting (3:8), by the application server, said response to said user equipment, said response comprising configuring data associated with said initiated configuration, the configuration data being associated with the unicast bearer preparation; receiving (3:9), by the user equipment, from said application server, the configuration data associated with said initiated configuration, the configuration data being associated with the unicast bearer preparation; and initiating, by the user equipment, a release phase, said release phase comprising releasing said multicast bearer, negotiating resources for a unicast bearer and subsequently requesting (3:14), via a trick play command comprising said configuration data, said content server to resume transmission of said media session via said unicast bearer, based on said configuration data, wherein said preparation phase and release phase are triggered by any of a splicing point in the received media stream, a timeout of timer, a trigger message, or a manual activation entered by a user of said user equipment.