In transfer scenario transferror send SIP/SDP packet. In SDP side, transferror puts “sendonly” and “Connection Information IP” as 0.0.0.0 and sends this packet to transferee.
Why transferror sends “sendonly” to transferee?it must be “sendrecv”?
What does at mean Connection Information as 0.0.0.0? It means that transfeee will not send packet??What does at mean if i write connection information as 0.0.0.0?
It’s a method of putting them on hold.
1 Like
yes but why transferror sends “sendonly” to transferee? What is the logical explanation?
Why transferror sends its “Connection Information” as 0.0.0.0?What is the logical explanation?
Friend i know it is for hold. I asked for learning logical side.
So that if they are connected to a platform or system that supports generating hold music they don’t hear absolutely nothing. If they didn’t then during the transfer process the line would be silent, which can cause some people to not know if they got disconnected or not and result in them hanging up.
“So that if they are connected to a platform or system that supports generating hold music they don’t hear absolutely nothing”–>means transferee will not hear anything even if i want to send hold music? But transferee can send media?
It… depends.
If you don’t put them on hold then you CAN provide a stream of media from your local source and they won’t know they are on hold. Phones don’t do this, though, and send hold so that something upstream (like a PBX) can generate the media.
What is the role of 0.0.0.0 IP address as a connection information? What does Transferee do when it gets 0.0.0.0 ip address in incoming SDP packet from its peer?
It’s an old method of signaling hold.
1 Like
it does not mean anything logically?
What it means and does is up to the implementation like I’ve described before…