[Spce-user] retries of INVITES for session timers

[Matthew Ogden]

Thanks again for your assistance Jon.

One last question, so I can track instances of this happening.

I have increased SEMS debug log level to 3.

What does it log if a call is terminated because the session timer expired?

(It is so verbose, I'm not sure I will notice it, and wil need to grep it).

Also, I assume these are normal course? DEBUG: Transaction timer expired:
type=K, trans=0xaf82e0, eta=129798194, t=129798194
Or is that what I'm looking for?

> -----Original Message-----
> From: Jon Bonilla (Manwe) [mailto:jbonilla at sipwise.com]
> Sent: 08 April 2013 01:49 PM
> To: spce-user at lists.sipwise.com
> Cc: Matthew Ogden
> Subject: Re: [Spce-user] retries of INVITES for session timers
>
> El Fri, 5 Apr 2013 19:09:23 +0200
> Matthew Ogden <matthew at tenacit.net> escribió:
>
> > Hmmm... here it comes then.
> >
> > Its asterisk who sent the 100, so its their responsibility to keep
> > sending the 200 until they get an Ack.
>
> Yes, I'd say so.
>
> >
> > Would anyone else like to comment?
> >
> > Would there be a way without disabling timers to get SEMS to
> > workaround this? (to go back to retrying the reINVITE?)
> >
> >
>
> Not without patching sems that I know.
>
> Why the 200 ok or its retransmissions are not reaching the system?
> Shouldn't we focus on that?