On 07.04.17 10:29, Daniel Tryba wrote:
> On Thu, Apr 06, 2017 at 06:52:55PM +0200, DanB wrote:
>> Many thanks again for premium support as always ;).
>> Will get back to them since I understand Kamailio is RFC compatible on this
>> one.
> Out of curiosity, what type of Avaya PBX are youy having
On Thu, Apr 06, 2017 at 06:52:55PM +0200, DanB wrote:
> Many thanks again for premium support as always ;).
> Will get back to them since I understand Kamailio is RFC compatible on this
> one.
Out of curiosity, what type of Avaya PBX are youy having problems with?
I only have seen IP Offices on
Hey Daniel,
Many thanks again for premium support as always ;).
Will get back to them since I understand Kamailio is RFC compatible on
this one.
Have a good one!
DanB
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
Hello,
tell them to read again the RFC3261, respectively the Via grammar:
Via = ( "Via" / "v" ) HCOLON via-parm *(COMMA via-parm)
via-parm = sent-protocol LWS sent-by *( SEMI via-params )
via-params= via-ttl / via-maddr
/ via-received /
Hey Daniel,
Indeed, call comes in over tcp and goes out over udp. They claim that it
is not RFC compatible to add the i.
Thanks,
DanB
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
Hello,
is the traffic coming to Kamailio via tcp?
Cheers,
Daniel
On 04.04.17 16:39, DanB wrote:
> Hey Guys,
>
>
> Any of you know which module is adding the "i" attribute and maybe if
> it can be removed safely? The reason would be for some Avaya PBXes
> discarding the Via completely due to
Hey Guys,
Any of you know which module is adding the "i" attribute and maybe if it
can be removed safely? The reason would be for some Avaya PBXes
discarding the Via completely due to this attribute.
Sample header:
"""
Via: SIP/2.0/UDP
