[reSIProcate] Strange issue: can't received the re-INVITE message

Scott Godin sgodin at sipspectrum.com
Tue Jul 21 11:56:51 CDT 2009


The logs indicate that the reINVITE has the exact same branch parameter /
transaction id as the original invite - so it is being discarded by the
stack.  Looks like the BYE message is also using the same transaction id -
however it comes in later, after the stack has discarded the original INVITE
transaction state, so it is accepted.
STACK | 20090721-124156.801 | MY TEL | RESIP:TRANSACTION | 1364 |
transactionstate.cxx:1606 | Dropping retransmitted INVITE in stale server
transactionSipReq:  INVITE 9199025012 at 192.168.1.188:6671 tid=1248151307347
cseq=INVITE contact=125.22.86.19:5060 / 3 from(wire)

Scott

On Tue, Jul 21, 2009 at 12:47 AM, Karlsson <boost.regex at gmail.com> wrote:

> Hi Scott, I have attached the stack log and wireshark file in email.
> Thank you in advance.
>
>
> On Tue, Jul 21, 2009 at 12:10 AM, Karlsson <boost.regex at gmail.com> wrote:
>
>> How to enable the stack level log ?
>> Thanks
>>
>>
>> On Mon, Jul 20, 2009 at 9:38 PM, Scott Godin <sgodin at sipspectrum.com>wrote:
>>
>>> In the resip trace the contact header in your 200 response (
>>> sip:9199025012 at 218.76.20.175:45151)  is different than your registration
>>> (sip:9199025012 at 192.168.1.188:6211) - but this appears to be OK, since
>>> the pcap trace shows the reINVITE going the correct location.  Can you
>>> provide a STACK level trace?
>>> Scott
>>>
>>> On Mon, Jul 20, 2009 at 6:55 AM, Karlsson <boost.regex at gmail.com> wrote:
>>>
>>>> Hi all, I got a very strange issue with 1.5, after the call is
>>>> established, when the caller(UAC) use re-INVITE to HOLD the call,
>>>> the callee can't received the re-INVITE message - but the re-INVITE
>>>> message is appears in the wireshark log.
>>>>
>>>> I have attached the log files in mail, log1.pcap of the callee, we can
>>>> saw the re-INVITE message is arrived,  but in the stack log - debug-log.txt,
>>>> we can't saw this INVITE.
>>>>
>>>> I have tested with eyeBeam, got the same result.
>>>>
>>>> Thanks
>>>>
>>>>
>>>> _______________________________________________
>>>> resiprocate-devel mailing list
>>>> resiprocate-devel at resiprocate.org
>>>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20090721/e8fbbbea/attachment.htm>


More information about the resiprocate-devel mailing list