Re: [SR-Users] kamailio not sending 202 after 408 is sent

Hi all, I have an edge proxy (E) and a registrar (R) behind it. In R, if a MESSAGE failed to deliver for any reason, R stores the MESSAGE in msilo. If the MESSAGE timed out, R sends a 408 time out first and then send a 202 Accepted after the MESSAGE is stored. The problem is, E happily forwards the 408 to the sender of the MESSAGE, but decides not to forward the 202. The log: DEBUG: t_reply_matching: hash 16662 label 0 branch 0 DEBUG: tm [t_lookup.c:1032]: DEBUG: t_reply_matching: reply matched (T=0x7f99eebb2ae0)! DEBUG: tm [t_lookup.c:1164]: DEBUG: t_check_msg: msg id=3 global id=3 T end=0x7f99eebb2ae0 DEBUG: tm [t_reply.c:2085]: DEBUG: reply_received: org. status uas=408, uac[0]=408 local=0 is_invite=0) DEBUG: tm [t_reply.c:1207]: ->>>>>>>>> T_code=408, new_code=202 DEBUG: tm [t_reply.c:1706]: DEBUG: relay_reply: branch=0, save=0, relay=-1 Can I change this behaviour to also forward the 202 withouting hacking in the source code? Regards, Allen _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users