Thanks Klaus.
-graham
On 2/7/11 7:13 AM, "Klaus Darilion" wrote:
>
>
> Am 07.02.2011 13:47, schrieb Graham Wooden:
>> The SIP Timer, no? When I do a sip trace, that is what I see come across
>> from avaya system in the options packets.
>
> If it is an OPTIONS request I guess it is just a k
Am 07.02.2011 13:47, schrieb Graham Wooden:
> The SIP Timer, no? When I do a sip trace, that is what I see come across
> from avaya system in the options packets.
If it is an OPTIONS request I guess it is just a keep-alive to keep the
NAT/FW bindings alive.
This could be fixed easily:
if (is_
The SIP Timer, no? When I do a sip trace, that is what I see come across
from avaya system in the options packets.
" Supported: timer"
-graham
On 2/7/11 2:16 AM, "Klaus Darilion" wrote:
>
>
> Am 06.02.2011 15:48, schrieb Graham Wooden:
>> The issue is that I am throwing back a 404 to them
Am 06.02.2011 15:48, schrieb Graham Wooden:
> The issue is that I am throwing back a 404 to them when they do a timer
> event, as they are passing sip:unkn...@my.ip.addr.
What is a 'timer event'?
regards
Klaus
___
SIP Express Router (SER) and Kamaili
The best way to handle this is using a static trusted IP trunk rather
than trying to spoof digest authentication mechanisms or fool the
location service.
--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961
Hi there,
I turned up a few new sip trunk customers this past week, from which one of
them was an Avaya system.
The customer wasn¹t able to do a username/password auth, so I set them up as
a permanent entry in the location table. I am running Kamailio 1.5.5.
The issue is that I am throwing back a
