module be configured to forward stored messages directly to the UA
contact address?
Thanks,
Owen Lynch
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
endif
return;
}
Thanks,
Owen Lynch
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
and try again,
>
> Wbr,
> Alexandr
>
>
> 2012/12/3 Owen Lynch
>
>>
>>
>>
>> On 3 December 2012 10:20, Alexandr Dubovikov wrote:
>>
>>> Hi Olwen,
>>>
>>> ** **
>>>
>>> siptrace use UDP to send HEP pa
when
trying to send an error reply. Can anyone shed any light on this?
Thanks,
Owen Lynch
Back trace:
Program terminated with signal 11, Segmentation fault.
#0 0x0813c916 in send2child (tcpconn=0xb55c1c60) at tcp_main.c:3967
3967tcp_main.c: No such file or directory.
in tcp_main.c
hanks,
Owen
On 7 November 2012 09:35, Owen Lynch wrote:
> Hi Paul,
>
> yes, I have the standard acc parameters set up. I have RADIUS logging of
> transactions working (start and stop events on call establishment and clear
> down) but not CDR events. I understand that CDR support
MISSED)
modparam("acc_radius", "radius_extra",
"Called-Station-Id=$tu;Calling-Station-Id=$fu")
# - dialog params -
modparam("dialog", "dlg_flag", 4)
#!endif
On 6 November 2012 20:52, Pawel Kuzak wrote:
> Hi Owen,
>
> I think bas
te script (e.g. setflag(FLD_DLG)) but I'm not
sure where. Should this be done in the INVITE and BYE method handling as is
currently done for the transaction accounting, e.g.:
# account only INVITEs
if (is_method("INVITE"))
{
setf
Hi,
I see Peter Dunkley's websocket work is not in the latest 3.3 release
(3.3.2). What is the road map for this?
Thanks,
Owen Lynch
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
all
further NOTIFY/INVITE requests. I thought that adding force_tcp_alias() in
the route script would accomplish this, but it doesn't. The NOTIFY always
uses the ip:port tuple specified in the SUBSCRIBE Contact header.
Can anyone shed any light on this?
Thanks,
Owen
all
further NOTIFY/INVITE requests. I thought that adding force_tcp_alias() in
the route script would accomplish this, but it doesn't. The NOTIFY always
uses the ip:port tuple specified in the SUBSCRIBE Contact header.
Can anyone shed any light on this?
Thanks,
Owen
10 matches
Mail list logo