Response overrides local tag?

"Kalman Lau" <[email protected]>
Newsgroups gmane.comp.voip.nist-sip
Message-ID <[email protected]>
For the following sequence...

Caller        App
------        ---
  |            |
  | INVITE     |
  +----------->|
  |            |
  |     Trying |
  |<-----------+
  |    Ringing |
  |<-----------+
  |         OK |
  |<-----------+
  |            |
  | ACK        |
  +----------->|
  |            |
  |      REFER |
  |<-----------+
  |            |
  | Accepted   |
  +----------->|
  | NOTIFY     |
  +----------->|
  |            |

I used the Dialog generated from the initial INVITE to send the REFER
request.  Was this appropriate?  If so, I am having the following problem...

The SIPClientTransaction was woken up to process the 202-Accepted response,
it proceeds to trigger the SIPDialog to update its local tag as follows:

+-> UDPMessageChannel.run() line: 452
  +-> SIPClientTransaction.processResponse(SIPResponse, MessageChannel)
line: 1252
    +-> SIPClientTransaction.processResponse(SIPResponse, MessageChannel,
SIPDialog) line: 521
      +-> SIPDialog.setLastResponse(SIPTransaction, SIPResponse) line: 2244
        +-> SIPDialog.setLocalTag(String) line: 1302

(Note:  line numbers from JAIN_SIP_1_2 as of last week...)

But being a server dialog, SIPDialog.setLastResponse() sets the local tag
using the response's TO header tag, thus overriding what appears to be its
original, valid local tag.

Subsequently, when the app attempts to respond to the NOTIFY with a
200-OK (using
the NOTIFY request's transaction), SIPServerTransaction.sendResponse(Response)
line 1252 throws a SipException with message "Response tags dont match with
Dialog tags".

Is the noted issue about the local tag a bug?  Or am I misusing something
else?

Kalman

_______________________________________________
nist-sip mailing list
[email protected]
http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.