o Juha Heinanen on 02/27/2012 07:34 AM:
i have not been able to figure out is it possible for sbc have two
outbound proxies: one for the incoming leg and the other for outgoing
leg.
the idea is that if sbc sits between inside and outside worlds, it
should use a given outbound proxy when request comes from outside and
goes inside and for in-dialog session timer re-invites use outside
outbound proxy when it sends re-invites to outside ua and use inside
outbound proxy when it sends re-invites to inside ua.
any suggestions on how to achieve the above or arguments on why the
above configuration does not make sense?
the SBC profile's outbound_proxy proxy is used only for the B leg. On
the A leg, when the INVITE comes in through a record routing proxy,
all requests back there should traverse that proxy.
Other than that, the outbound proxy defaults to the outbound_proxy
configured in sems.conf. So you can set both by configuring the one
for A in outbound_proxy in sems.conf, and the one in B in the profile
conf.
one of the applications is when sems sbc sits between outside world and
a sems application, such as voicemail:
ua - public internet - proxy - sems sbc - sems application
when session timer is on, re-invites to ua should use proxy and
re-invites to sems app should go direct.
this looks more like you would use next_hop directly, doesn't it?
Stefan
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
