| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
|
If DUM receives an invite with a call-id and from-tag matching
an existing DialogSet, then it will dispatch the message to that DialogSet, and
end up creating a new Dialog. This should cause a new call to the onNewSession
callback. If your application wants to reject such requests then it can
do one of a few things: 1.
Check if the AppDialogSet is the same in both invites and reject
the 2nd one. 2.
Check if the DialogId is the same in both invites in reject the
2nd one. However, be warned that this scenario is expected on an initial
invite, when forking occurs. Scott From:
resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of alexzhang@xxxxxxxxxxx Hi, Here is an error handling, that the
UAS receives a re-invite without To tag while it contains the same Call-ID and
>From Tag with that of the exisiting established dialog. Hence, this kind of
invalid Re-invite should be detected and discarded. Please let me know which
part of the code of the Resiprocate is reponsible for such a case? Please
forgive me for this preliminary question. Thanks, Alex Zhang GSM/UMTS Voice Core - MSC Design Guangdong Nortel (GDNT) R&D Center PSTN: +86 020 89188782 / ESN: 6 554 8782 E-Mail: alexzhang@xxxxxxxxxxx /
YahooIM: zcc_nuaa " Stay Hungry, Stay
Foolish." - Steve Jobs |