when invite request comes to sbc application and includes these headers:
P-App-Name: sbc
P-Call-Control: ctl;append_headers=P-App-Name: announcement
P-Call-Control: ctl;outbound_proxy=sip:127.0.0.1:5090
P-Call-Control: ctl;force_outbound_proxy=yes
P-Call-Control: ctl;next_hop_ip=
P-Call-Control: ctl;next_hop_port=
sems sends outgoing invite out correctly to the specified outbound
proxy.
if i leave out these two headers:
P-Call-Control: ctl;next_hop_ip=
P-Call-Control: ctl;next_hop_port=
sems sends outgoing invite to sip:127.0.0.1:5080, which is according to
what i have specified in sems.conf:
outbound_proxy=sip:127.0.0.1:5080
force_outbound_proxy=yes
why are the two headers required in order to make sems obey
call_control:ctl outbound_proxy specification? is it a bug or feature?
weird thing is that sems gets correct outbound_proxy info from incoming
request, but does not use it. instead, it sets destination based
sems.conf info:
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [parse_sip_uri, parse_uri.cpp:332]
DEBUG: Converted URI port (5090) to int (5090)
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [set_destination_ip,
trans_layer.cpp:715] DEBUG: checking whether '127.0.0.1' is IP address...
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [set_destination_ip,
trans_layer.cpp:757] DEBUG: set destination to 127.0.0.1:5080
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [send_request,
trans_layer.cpp:883] DEBUG: send_request to R-URI <sip:[email protected]>
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [parse_sip_uri, parse_uri.cpp:332]
DEBUG: Converted URI port () to int (5060)
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [parse_via_params,
parse_via.cpp:525] DEBUG: parsed branch: z9hG4bKDGPzZa4X
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [parse_via_params,
parse_via.cpp:548] DEBUG: has_rport: 1
Feb 23 04:28:33 sip sems[27532]: [#b49d2b70] [send_request,
trans_layer.cpp:952] DEBUG: Sending to 127.0.0.1:5080 <INVITE
sip:[email protected] SIP/2.0#015#012Via: SIP/...>
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
