[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: Kamailio.cfg disptacher function example:
{ 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:
{ 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 |
Best regardsThe msg are: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.Thank you
- 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)
- 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
--José Seabra