Stiles, They haven't resolved it yet. I'm just working around the issue for the time being while I consider moving to another ISTP. I like Flowroute, but perhaps they are not the best match for Sipx.
Dan On Thu 09.Dec.10 13:21, Stiles Watson wrote: >Dan, > >Any solution on this? > >Stiles > >Dan McDaniel wrote: >> Yes, we are still working on this, but it's not resolved yet. Turns out >> that 30 minutes (1800 seconds) is the time in the Session Timer Interval >> box on the gateway setup screen. It controls what goes into the Session >> Expires header in the INVITE. This is all described in RFC4028. >> >> In my INVITE I send >> >> Session-Expires: 1800;refresher=uac >> >> If the ISTP sends the same header back in the 200 then we are all set. >> Flowroute doesn't include any header in their 200 response. This is OK >> too, and means that there will not be any Session Expires timer in >> effect for the call. But then they drop the call at the 30-minute mark. >> >> I've tried setting this to different values and the call is always >> dropped when the interval expires. >> >> According to Flowroute and the ULC (and they continue to say that the >> problem goes back to the ULC) they don't use the session timer at all. >> Yet, they keep dropping the calls at that exact time. >> >> Hint: if you're going to be debugging this set the value to 600. That's >> the lowest value that works (at least with Flowroute). It's a lot easier >> to run a series of 10-minutes calls. >> >> Our last call trace was on Friday. Waiting to hear back. >> >> Dan >> _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
