On 4/3/12 2:51 PM, James Ryan wrote:
We are currently having an argument with a vendor regarding how the handle
media streams during the REFER process. We are issuing a REFER request to
our peer after placing them on sendonly hold per the standard practice in
RFC3515. In processing the
From: James Ryan [jr...@computer-talk.com]
Our implementation continues to stream silence to the transferee while
the transferee begins to play out the early media data. In this
scenario, the UA interleaves our silence packets with the early media
packets from the third party.
There have
with 183-Early
Media from the third party
On 4/3/12 2:51 PM, James Ryan wrote:
We are currently having an argument with a vendor regarding how the
handle media streams during the REFER process. We are issuing a REFER
request to our peer after placing them on sendonly hold per the standard
We are currently having an argument with a vendor regarding how the handle
media streams during the REFER process. We are issuing a REFER request to our
peer after placing them on sendonly hold per the standard practice in RFC3515.
In processing the REFER our peer receives a 183 from the
