o Juha Heinanen on 05/19/2011 07:24 PM:
Stefan Sayer writes:
ok. just a minor correction: setting outbound_proxy in sems.conf is
ok, setting force_outbound_proxy possibly not.
after cherry picking the last commit to 1.4, i now have in sems.conf:
outbound_proxy=sip:127.0.0.1:5080
#force_outbound_proxy=yes
next_hop_ip=127.0.0.1
next_hop_port=5080
when conf_auth app sends re-invite to ua that includes ip/port info of
the conference in its sdp, wireshark shows that it is NOT send to 127.0.0.1
at port 5080, but to 192.98.102.10 at port 5060, i.e., the above is not
honored. route headers are now ok.
are you sure you picked the right commit? I'm testing here with
ann_b2b (which essentially does the same), and it sends the reinvite
to next_hop_ip:next_hop_port which is 192.168.5.106:5062 in my case.
e.g. I get this:
[#b64f2b70/24740] [sendEstablishedReInvite, AmB2BSession.cpp:590]
DEBUG: sending re-INVITE with saved session description
[#b64f2b70/24740] [sendRequest, AmSipDialog.cpp:1034] DEBUG:
next_hop=192.168.5.106:5062
[#b64f2b70/24740] [parse_sip_uri, parse_uri.cpp:332] DEBUG:
Converted URI port () to int (5060)
[#b64f2b70/24740] [set_destination_ip, trans_layer.cpp:683] DEBUG:
checking whether '192.168.5.106' is IP address...
[#b64f2b70/24740] [set_destination_ip, trans_layer.cpp:725] DEBUG:
set destination to 192.168.5.106:5062
[#b64f2b70/24740] [send_request, trans_layer.cpp:820] DEBUG:
send_request to R-URI <sip:[email protected]:2048;line=jcn1m7zz;ob>
[#b64f2b70/24740] [parse_sip_uri, parse_uri.cpp:332] DEBUG:
Converted URI port (2048) to int (2048)
[#b64f2b70/24740] [parse_via_params, parse_via.cpp:525] DEBUG:
parsed branch: z9hG4bKE2nE~avt
[#b64f2b70/24740] [parse_via_params, parse_via.cpp:548] DEBUG:
has_rport: 1
[#b64f2b70/24740] [send_request, trans_layer.cpp:889] DEBUG: Sending
to 192.168.5.106:5062 <INVITE
sip:[email protected]:2048;line=jcn1m...>
can you PM/post me a debug log of the same region?
also, my proxy still complains about 200 ok from sems not belonging to
any transaction. looks like conf_auth app does not match the ack
properly that it receives from conference app to the re-invite that
conf_auth sent to conference app.
this is a different issue, which makes SEMS match ACK that it sends
through proxy to itself back to the uac transaction instead of the uas
transaction.
Stefan
-- juha
--
Stefan Sayer
VoIP Services Consulting and Development
Warschauer Str. 24
10243 Berlin
tel:+491621366449
sip:[email protected]
email/xmpp:[email protected]
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
