Re: [reSIProcate-users] how can i use 18x provisional response with reliability]
--- Begin Message ---
Thanks Scott. I have added 100rel as a supported option tag. But now the
problem I am facing is in callee side. How can I generate a provisional
message with offer/answer? The existing provisional function does not
provide this. What should the flow be like if I make a offer in the
invite and send a answer in the 18x response from the callee side? Also,
what should the caller do after receiving this 18x message, if PRACK is
not implement in DUM? How can this be implemented? It will be very
helpful if you point out some directions.
Thanks again. Best regards,
-Tanim.
Scott Godin wrote:
Looks like you need to add a 100rel as a supported option in the
MasterProfile. Take a look at
DialogUsageManager::validateRequiredOptions to see the code that is
getting triggered.
Also Note: Apparently UAS PRACK support is not currently implemented
in DUM. See the comments in MasterProfile.hxx (ln51) for more
information on the PRACK support in DUM.
Cheers,
Scott
On Thu, Nov 20, 2008 at 2:04 AM, Tanim <tanim@xxxxxxxxxxxxxxxx> wrote:
Hello,
I am trying to develop a phone based on voip and I am using the resiprocate
sip stack. I want to implement provisional response with reliability in
this. I set the UacReliableProvisionalMode to Required and
UasReliableProvisionalMode to Supported. But in the callee side, it is
generating a 420 message. What am i doing wrong? I found out that the first
invite message could have any of the reliableProvisionalMode. What should be
my course of action? I am using DUM. What the flow should be like if I make
an offer in the INVITE request with a require field with 100rel.
Thanks in advance. Best regards.
-Tanim
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.8/1801 - Release Date: 11/20/2008 9:11 AM
--- End Message ---