27 May
2016
27 May
'16
6:32 p.m.
Hi there,
The question is still relevant.
It seems to me that the problem lies somewhere in this part.
route[REPLY] {
route(ACCOUNTING);
t_on_reply("1");
t_on_failure("1");
if(is_present_hf("Proxy-Authorization"))
{
remove_hf("Proxy-Authorization");
};
xlog("L_INFO", "Request leaving server - M=$rm RURI=$ru F=$fu
T=$tu
IP=$si ID=$ci\n");
if (!t_relay()) {
if (method=="INVITE" || method=="ACK") {
route(RTPPROXY);
};
sl_reply_error();
};
exit;
}
2016-05-17 17:53 GMT+03:00 Daniel Tryba <d.tryba(a)pocos.nl>nl>:
On Tue, May 17, 2016 at 05:08:45PM +0300, Mx R wrote:
In our network we used several ONT Huawei models.
But with one model
HUAWEI-EchoLife HG8245 / V1R003C00S205 we have the following problem.
When
connecting to this device in the POTS ports of
the two phones. From the
first port we can not call to the second and from the second port can not
call to the first port. On the other ONT Huawei devices, there is no such
problem. Earlier we had set OpenSIP and this device did not have a
problem.
The problem is likely in the configuration because it works at the
default
settings.
In the past I ran into other devices/PBXs that can't handle the fact
there is an outgoing/incoming call with the same callid. You could try
the topoh module (with modparam("topoh", "mask_callid", 1))
Beware that it might introduce other problems in some calls scenarios,
my prefered solution is to route the call to a b2bua (asterisk) when I
detected hairpinning.
_______________________________________________
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