Hello Henning,

Yes this is correct, this reply came from UAS. We got this correctly. But we want to get, which kamailio sent to UAC side.

This following reply, we want to get by onreply_route

3(23) DEBUG: <core> [core/msg_translator.c:2306]: generate_res_buf_from_sip_res(): copied size: orig:130, new: 16, rest: 773 msg=
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.32.100.100:5055;branch=z9hG4bK-254-1-0
Record-Route: <sip:172.32.0.6:5060;lr;ftag=1>
Call-ID: T1_MYSER
From: <sip:caller@172.32.100.100>;tag=1
To: "callee" <sip:3228090000@172.32.0.6>;tag=6fb31703-d630-4140-a41b-7270cdcae85b
CSeq: 1 INVITE
Server: MYX Callcontrol
Contact: <sip:172.32.10.70:5060>
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, REGISTER, MESSAGE, REFER
Supported: timer, replaces, norefersub
Remote-Party-ID: <sip:s@172.32.0.6>;privacy=off;screen=no
Content-Type: application/sdp
Content-Length: 178

v=0
o=- 53655765 2353687639 IN IP4 172.32.10.70
s=session
c=IN IP4 172.32.10.70
t=0 0
m=audio 10006 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
a=maxptime:150
a=sendrecv

Thanks,

Salah

On Thu, Aug 22, 2019 at 2:52 PM Henning Westerholt <hw@skalatan.de> wrote:

(moved the discussion to user list)

Hello Salah,

I see the this output in the log message:

6(26) INFO: <script>: on_reply_route [SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.32.0.6;rport=5060;received=172.32.0.6;branch=z9hG4bKe68a.99dc492fe74dcfe1017828521a5fa362.0

2(22) INFO: <script>: on_reply_route [SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.32.0.6;rport=5060;received=172.32.0.6;branch=z9hG4bK178a.79cddb135aabfc42736fd9e9fd826ba8.0

and so on.. So you are seeing the replies correctly, or I wrong?

Cheers,

Henning

Am 22.08.19 um 21:29 schrieb Salah Ahmed:
Hello Henning,

We already added xlog in the onreply_route and found all messages in between kamailio and UAS. The attached log files in first email has those logs. If any other specific log needed I am here to provide them.

Thanks,

Salah
On Thu, Aug 22, 2019 at 2:24 PM Henning Westerholt <hw@skalatan.de> wrote:
Hello Salah,

ok, see if you are able to output some easy log with "xlog" in this route, to make sure there is no cfg problem somewhere.

Cheers,

Henning

Am 22.08.19 um 21:15 schrieb Salah Ahmed:
Hello Henning,

Thanks for quick reply, We armed the t_on_reply just before t_relay() in the route block.

t_on_reply("LOGRPL");
if (!t_relay()) {
sl_reply_error();
}

Thanks,

Salah
On Thu, Aug 22, 2019 at 2:03 PM Henning Westerholt <hw@skalatan.de> wrote:
Hello Salah,

the replies are going from the UAS to the UAC over Kamailo as a proxy, with the exception of the hop-by-hop 100.

So you should see the 200 OK in the Kamailio in reply_route and onreply_route. Maybe you can check if you armed the onreply_route with t_on_reply for the INVITE routing.

Cheers,

Henning

Am 22.08.19 um 19:50 schrieb Salah Ahmed:
Hello,

We facing an issue on capturing sip message in Kamailio(Version: 5.2.3). The scenario is very simple.

UAC Kamailio UAS

|--------INVITE--------->| |

| |-------INVITE------->|

| |<------100 Trying----|

|<-------100 Trying------| |

| |<------200 Ok--------|

|<-------200 Ok----------| |

In this simple scenario, we can't catch any reply messages in between the Kamailio and UAC. We have tried reply_route, onreply_route, and onsend_route. But no one work to grep that reply on that side. onsend_route was bad try as its only for forwarded reply message. Is there any other magic to capture those replies. A debug=3 log message attached here.

Thanks,

Salah
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services