In practice, there is no "typical" way of putting a call on hold. The very
meaning of that action is highly dependent on what you are looking at. If
you are looking at signaling coming from an IP phone, you seldom get
a=sendonly when someone is placing a call on hold. You will only see that
when so
Ranjit Avasarala writes:
> Another way to check is the SDP. for hold music, the media attribute will
> be sendonly. where as for regular voice traffic it will sendrecv
Yes, the "typical" way to tell that the far end has put you on hold is
that they will send you a=sendonly in the SDP. Of cour
Arun,
On 9/22/22 10:56 AM, Arun Tagare wrote:
Thanks Ranjit,
Yes for the signalling part i am aware, but as shared earlier how the RTP
from N/w and other UE in same session be differentiate?
So SSRC will be different right?
*Nothing* is certain here!
The SSRC may be different, but not neces
Thanks Ranjit and Roman, will go over the link.
On Thu, 22 Sep 2022 at 8:40 PM, Roman Shpount wrote:
> Arun,
>
> Depending on the scenario, nothing will be different. You cannot rely on
> signaling or SSRC. The calling parting can be behind the PSTN gateway and
> continue to send audio regardles
Arun,
Depending on the scenario, nothing will be different. You cannot rely on
signaling or SSRC. The calling parting can be behind the PSTN gateway and
continue to send audio regardless of the hold state on the origination
side. The only way to differentiate is to check the actual audio content.
Hi Arun
you won't get RTP from NW and end point at the same time. consider this
scenario: User Alice calls User Bob. Now Bob is busy with other call. So
here User Alice will hear a hold tone i.e busy signal and would get 486
Busy here. Here SSRC would be server . So now Alice will not get any
Thanks Ranjit,
Yes for the signalling part i am aware, but as shared earlier how the RTP
from N/w and other UE in same session be differentiate?
So SSRC will be different right?
On Thu, 22 Sep 2022 at 8:05 PM, Ranjit Avasarala
wrote:
> Hi Arun
>
> Both are technically voice packets and use RTP
Hi Arun
Both are technically voice packets and use RTP protocol. So that way both
are similar. Also the voice traffic is end to end whereas hold music is
from the server. Like announcement - may be from Application Server. So
looking at the SSRC or Source in RTP Packets, you should be able to
Arun, for what purpose would you like to inspect and differentiate the hold
and audio RTP packets?
and based on the signaling messages, can't that be achieved.
Thanks,
Amanpreet Singh.
On Thu, Sep 22, 2022 at 12:30 PM Arun Tagare wrote:
> Thanks Ranjit & Amanpreet, for your response
>
> But my
Thanks Ranjit & Amanpreet, for your response
But my question is
MT <= Call Established ===> MO
MT <===> Voice RTP Packets flow <=> MO
MT <==Hold ===> MO
MT < HOLD Tone RTP packets == NW
Both Voice RTP packets and Hold RTP packets come to the same port
Probably you can think of looking into the signaling messages(SDP in case
of SIP) to differentiate when the call is on hold and when not i.e. normal
audio RTP.
BTW what is the use case to differentiate call hold vs audio RTP?
Regards,
Amanpreet Singh.
On Wed, Sep 21, 2022 at 9:51 PM Arun Tagar
Hi All,
I have a doubt on the Hold call tone or music on hold tone RTP v/s actual
voice RTP before hold
Can these RTP packets be able to differentiate?
If yes how?
if not why?
Thanks a lot to everyone in advance
--
With Regards
Arun A. Tagare
+91 9449 029729
_
12 matches
Mail list logo
