6 Sep
2017
6 Sep
'17
4:43 p.m.
Hello there,
I'm facing some error msg on my kamailio server in production that i would
like to understand what they means in order to avoid them.
The msg are:
- *ERROR: tm [t_reply.c:1270]: t_should_relay_response(): ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 200*
- *dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load for
(16720.mydomain.com <http://16720.mydomain.com>)*
- *dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 603 was sent out*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 480 was sent out*
- *WARNING: tm [t_lookup.c:245]: ack_matching(): WARNING: ack_matching()
attempted on a transaction with no E2EACK callbacks => the results are not
completely reliable when forking is involved*
Thank you
Best regards
--
José Seabra
9 Sep
9 Sep
4:49 p.m.
Hi There,
Regarding to this error:
- *dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load for
(16720.mydomain.com <http://16720.mydomain.com/>)*
- *dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution*
The reason could be because i'm not using the disptcher function
"ds_load_update()" and "ds_load_unset()" on my script logic??
Thanks
BR
José
2017-09-06 14:43 GMT+01:00 José Seabra <joseseabra4(a)gmail.com>om>:
Hello there,
I'm facing some error msg on my kamailio server in production that i would
like to understand what they means in order to avoid them.
The msg are:
- *ERROR: tm [t_reply.c:1270]: t_should_relay_response(): ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 200*
- *dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load
for (16720.mydomain.com <http://16720.mydomain.com>)*
- *dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 603 was sent out*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 480 was sent out*
- *WARNING: tm [t_lookup.c:245]: ack_matching(): WARNING:
ack_matching() attempted on a transaction with no E2EACK callbacks => the
results are not completely reliable when forking is involved*
Thank you
Best regards
--
José Seabra
--
Cumprimentos
José Seabra
11 Sep
11 Sep
11:25 a.m.
Hello,
On 06.09.17 15:43, José Seabra wrote:
Hello there,
I'm facing some error msg on my kamailio server in production that i
would like to understand what they means in order to avoid them.
The msg are:
* /ERROR: tm [t_reply.c:1270]: t_should_relay_response(): ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408,
received: 200/
/A 200 ok response was received after a (likely local) retransmission
timeout./
/
/
* /dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load
for (16720.mydomain.com <http://16720.mydomain.com>)/
* /dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution/
/Have you set the attributea for load distribution in the dispatcher
record for that destination?
/
/
/
* /tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 603 was sent out/
* /tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 480 was sent out/
Likely a CANCEL was received after sending out a final response.
/
/
* /WARNING: tm [t_lookup.c:245]: ack_matching(): WARNING:
ack_matching() attempted on a transaction with no E2EACK callbacks
=> the results are not completely reliable when forking is involved/
This needs a look in the code, haven't written that part so I don't know
by heart the purpose ...
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
12 Sep
12 Sep
10:53 p.m.
Hello Daniel,
Thank you for your clarifications, it was helpfull.
Regarding to the Dispatcher error, please see my comment in yellow:
-
* dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load for
(16720.mydomain.com <http://16720.mydomain.com/>)*
- *dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution*
*[Daniel]: Have you set the attributea for load distribution in the
dispatcher record for that destination?*
*[José] :the only load distribution that i set was in dispatcher.list
file(I didn't understand if was here that you is reffering the attributes),
on my script i only use the function ds_select_dst("9","10").*
*Dispatcher.list file example:*
9 sip:IP:5080 0 1 duid=PRX1;my=prx1;maxload=20000
*Kamailio.cfg disptacher function example: *
if(!ds_select_dst("9", "10"))
{
xlog("L_ERR", "Failed to select proxy - R=$ru ID=$ci
UA='$ua'\n");
sl_send_reply("503", "No proxy available, try again
later");
exit;
}
I also have a failure route to select the another available destinations:
if(!ds_next_dst())
{
xlog("L_INFO", "PRX FAILURE no proxy availabe
ID=$ci\n");
send_reply("503", "No proxy available, try
again later");
exit;
}
Once again, thank you for the support. Best Regards José Seabra
2017-09-06 14:43 GMT+01:00 José Seabra <joseseabra4(a)gmail.com>om>:
Hello there,
I'm facing some error msg on my kamailio server in production that i would
like to understand what they means in order to avoid them.
The msg are:
- *ERROR: tm [t_reply.c:1270]: t_should_relay_response(): ERROR:
t_should_relay_response: status rewrite by UAS: stored: 408, received: 200*
- *dispatcher [dispatch.c:1509]: ds_load_replace(): cannot find load
for (16720.mydomain.com <http://16720.mydomain.com>)*
- *dispatcher [dispatch.c:2270]: ds_next_dst(): cannot update load
distribution*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 603 was sent out*
- *tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't
generate 487 reply when a final 480 was sent out*
- *WARNING: tm [t_lookup.c:245]: ack_matching(): WARNING:
ack_matching() attempted on a transaction with no E2EACK callbacks => the
results are not completely reliable when forking is involved*
Thank you
Best regards
--
José Seabra
--
Cumprimentos
José Seabra
2632
days inactive
2638
days old
3 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
José Seabra