Milan,
On putting a call on hold, your product should prefer and support
the '3264 Offer/Answer' RFC method of placing a call on hold by using the
sendonly attribute in the SDP of the INVITE.
RFC 3515 is for the REFER method which you will be using for the
Call transfer scenarios the forming and processing a REFER message are
detailed in this. If I had some more time I could include a ladder diagram
of what the signalling looks at but work here uses a B2BUA and I wouldn't
want that to confuse your expectation of what should be happening.
Regards,
Wayne Davies
Hi,
I am in the process of testing Call Xfer Blind & Attended , Call Forward
feature for our product. I would like to know what are the field values in
each packets exchanged between the 2 UAs that I should look for to prove
the same works for my product.
Eg : SIP Phone A makes call to SIP Phone B. RTP Packets get Xchanged
between the 2 UAs. SIP Phone B puts the same call on Hold.
In this eg: I need to check the "c" field in the Re-INVITE packet sent
from
SIP Phone B to SIP Phone A with the value "C=IN IP4 0.0.0.0 to prove that
the call is actually on hold apart from the fact that RTP packets do not
get exchanged between the 2 UAs while the call is on hold.
Likewise, what do I need to check for Call Transfer (Blind & Attended) and
Call Forward??? Any good pointers to test the same features would be
highly
appreciated.
Thanks in advance...
Regards,
Milan Sengupta.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
******************************************************************************
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged
information. If you have received this email in error, please notify the sender and
delete it immediately.
Internet communications are not secure. You should scan this message and any
attachments for viruses. Under no circumstances do we accept liability for any loss
or damage which may result from your receipt of this message or any attachments.
******************************************************************************
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
