[Spce-user] Spce timeout for T.38 Reinvites
Ivan Milivojevic
edesibe at gmail.com
Mon Jan 20 06:34:54 EST 2014
Hi Mattwhew,
Can you paste logs from proxy and lb?
Regards,
Ivan
On Mon, Jan 20, 2014 at 11:54 AM, Matthew Ogden <matthew at tenacit.net> wrote:
> As per
> http://kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_set_fr
>
> (I see it is used else where in the proxy.tt2 file too).
>
>
>
> I tried putting this in proxy.custom.tt2 line 1076 (part of ROUTE_PSTN)
>
>
>
> #our fax testing is on subscriber with ext ID TN001FAX
>
>
>
> if($avp(s:caller_ext_subscriber_id) == "TN001FAX")
>
> {
>
> t_set_fr(30000);
>
> xlog("L_INFO", "Changed outbound timer for this call to
> 30000ms for faxing\n");
>
> }
>
>
>
> It logs it my proxy log, but 9 seconds is still the timeout of the INVITE
>
>
>
> *From:* Matthew Ogden [mailto:matthew at tenacit.net]
> *Sent:* 19 January 2014 06:36 PM
> *To:* 'Ivan Milivojevic'
> *Cc:* 'Spce-user'
> *Subject:* RE: [Spce-user] Spce timeout for T.38 Reinvites
>
>
>
> Thanks Ivan
>
>
>
> That’s definitely what I’m looking for, but perhaps someone out there can
> tell me in which section of the proxy/lb that I can have an override of the
> timer based on the subscriber name only. (I only need one subscriber with a
> much longer timeout).
>
>
>
> Regards
>
>
>
> *From:* Ivan Milivojevic [mailto:edesibe at gmail.com <edesibe at gmail.com>]
> *Sent:* 19 January 2014 04:51 PM
>
> *To:* Matthew Ogden
> *Cc:* Spce-user
> *Subject:* Re: [Spce-user] Spce timeout for T.38 Reinvites
>
>
>
> Hi Matthew,
>
> Maybe you can try with
> fr_timer_avpcheck also http://www.iptel.org/faq/sertimers
>
> Regards,
>
> Ivan
>
>
>
>
>
> On Sat, Jan 18, 2014 at 9:56 AM, Matthew Ogden <matthew at tenacit.net>
> wrote:
>
> Thanks Ivan!
>
>
>
> There is obviously no way to make kamailio have different timeouts for
> different INVITE (T.38 vs the rest) types then?
>
>
>
> *From:* Ivan Milivojevic [mailto:edesibe at gmail.com]
> *Sent:* 17 January 2014 08:58 PM
> *To:* Matthew Ogden
> *Cc:* Spce-user
> *Subject:* Re: [Spce-user] Spce timeout for T.38 Reinvites
>
>
>
> HI Matthew,
>
> You can check timeout on kamailio-proxy side...
>
> # kamailio.cfg.tt2
>
> modparam("tm", "fr_timer", 9000) ### based on doc ### Timer which hits if
> no final reply for a request or ACK for a negative INVITE reply arrives (in
> seconds).
> modparam("tm", "fr_inv_timer", 180000)
>
> Regards,
>
> Ivan
>
>
>
>
>
> On Fri, Jan 17, 2014 at 6:07 PM, Matthew Ogden <matthew at tenacit.net>
> wrote:
>
> HI
>
>
>
> What sets the timeout for a T38 reinvite on SPCE? My timeout is 4000ms for
> Sems in config.yml, so clearly its not that, since this took exactly
> 9000ms.
>
>
>
> What timer/timeout made my SIP server cancel the reinvite? The reason I
> need a longer timeout is, the recipient company is answering the call, then
> forwarding the through a few rings (extra time before the sync can actually
> be caught for t.38).
>
>
>
> in this wireshark call graph,
>
> The left line is my subscriber,
>
> The middle line is sipserver
>
>
>
> Here is picture,
>
>
>
> Below and attached are the text representation
>
> Conv.| Time | subscriber |
> Peer |
>
> | | | my server |
>
> 2 |18:46:27.453879| INVITE SDP (g711A)
> | |SIP From: <sip:2XXXXXXXXX at subscriberip:5060
> To:<sip:0XXXXXXXXX at spceIP:5060
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:27.454546| 100 Trying|
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
> 2 |18:46:27.456403| 407 Proxy Authentication Required
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
> 2 |18:46:27.510806| ACK |
> | |SIP Request
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:27.514119| INVITE SDP (g711A) |
> |SIP From: <sip:2XXXXXXXXX at subscriberip:5060
> To:<sip:0XXXXXXXXX at spceIP:5060
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:27.514636| 100 Trying|
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
>
> -----------------------------------------------------------------------------
>
> 3 |18:46:27.522117| | INVITE SDP
> (g711A) |SIP From: <sip:2XXXXXXXXX at subscriberipTo:<sip:2XXXXXXXXXX at peerip
>
> | | |(5060) ------------------> (5060)
> |
>
> 3 |18:46:27.536103| | 100 Giving a
> try |SIP Status
>
> | | |(5060) <------------------ (5060)
> |
>
> 3 |18:46:28.648929| | 200 OK SDP
> (g711A) |SIP Status
>
> | | |(5060) <------------------ (5060)
> |
>
>
> -----------------------------------------------------------------------------
>
> 2 |18:46:28.650490| 200 OK SDP (g711A)
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
> 2 |18:46:28.708976| ACK |
> | |SIP Request
>
> | |(5060) ------------------> (5060) |
> |
>
>
> -----------------------------------------------------------------------------
>
> 3 |18:46:28.710179| | ACK
> | |SIP Request
>
> | | |(5060) ------------------> (5060)
> |
>
>
> -----------------------------------------------------------------------------
>
> 2 |18:46:28.712202| INVITE SDP (t38)
> | |SIP From: <sip:2XXXXXXXXX at subscriberip:5060
> To:<sip:0 at spceIP:5060
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:28.712970| 100 Trying|
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
>
> -----------------------------------------------------------------------------
>
> 3 |18:46:28.713577| | INVITE SDP
> (t38) |SIP From: <sip:2XXXXXXXXX at subscriberipTo:<sip:2XXXXXXXXXX at peerip
>
> | | |(5060) ------------------> (5060)
> |
>
> 3 |18:46:28.717171| | 100 Giving a
> try |SIP Status
>
> | | |(5060) <------------------ (5060)
> |
>
>
> -----------------------------------------------------------------------------
>
> 2 |18:46:37.713078| 408 Request Timeout
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
> 2 |18:46:37.768451| ACK |
> | |SIP Request
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:37.770487| BYE |
> | |SIP Request
>
> | |(5060) ------------------> (5060) |
> |
>
> 2 |18:46:37.771110| 100 Trying|
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
> 2 |18:46:37.772098| 200 OK |
> | |SIP Status
>
> | |(5060) <------------------ (5060) |
> |
>
>
> -----------------------------------------------------------------------------
>
> 3 |18:46:37.772169| | ACK
> | |SIP Request
>
> | | |(5060) ------------------> (5060)
> |
>
> 3 |18:46:37.772244| | BYE
> | |SIP Request
>
> | | |(5060) ------------------> (5060)
> |
>
> 3 |18:46:37.776329| | BYE
> | |SIP Request
>
> | | |(5060) <------------------ (5060)
> |
>
> 3 |18:46:37.776817| | 200 OK
> | |SIP Status
>
> | | |(5060) ------------------> (5060)
> |
>
> 3 |18:46:37.778354| | 200 OK
> | |SIP Status
>
> | | |(5060) <------------------ (5060)
> |
>
> 3 |18:48:28.920672| | 408 Request
> Timeout |SIP Status
>
> | | |(5060) <------------------ (5060)
> |
>
> 3 |18:48:28.921215| | ACK
> | |SIP Request
>
> | | |(5060) ------------------> (5060)
> |
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140120/2104fdb7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 46251 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140120/2104fdb7/attachment-0001.png>
More information about the Spce-user
mailing list