Udit,
Please excuse my ignorance but can you explain / point me to the
draft RFC that covers how this works ?. If you finish the initial A to B
call, either party hanging up sends a BYE - the session and dialog will end
OR did the initial call setup with pre-paid verification created a dialog
that exists beyond the A to B call | session (3PCC server is B2BUA or
something ?).
Assuming the scenario is valid a UAS can respond with a 180 and I
would expect that it could be used to quench INVITE retransmissions and
trigger local ringback.
BUT..
In the scenario you describe below using 3PCC A is being INVITEd to
setup up the new call leg between A and C, so it is the UAS for this
request. So, it will be be doing the responses - 1xx, 200 OK and therefore
it wont receive a 180 ringing at all for the effect you were looking for.
Regards - Wayne.
Udit asked:
*********************************
>I want to know what should be the behaviour of UAC after receiving 180
>response when dialog is already in confirmed state.
>I think it should process it, is this behaviour mentioned anywhere in RFC?
>
>
>This scenario can occur in prepaid calling card application where user A
>first calls B, and after finsihing talking, he calls another user C on the
>same call.
>To connect user C, we can send Re-invite to user A agent resulting in call
>connected between A and C as per thirdparty call control.
>
>But before the call is answered by user C, if 180 Ringing is send to user
>agent A, it should play ringback as user need to hear the ringback to know
>the status of the second call.
>
>-Udit
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
**********************************************************************
Any personal or sensitive information contained in this email and
attachments must be handled in accordance with the Victorian Information
Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988
(Commonwealth), as applicable.
This email, including all attachments, is confidential. If you are not the
intended recipient, you must not disclose, distribute, copy or use the
information contained in this email or attachments. Any confidentiality or
privilege is not waived or lost because this email has been sent to you in
error. If you have received it in error, please let us know by reply
email, delete it from your system and destroy any copies.
**********************************************************************
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
