2010/6/18 Iñaki Baz Castillo :
> 2010/6/17 Klaus Darilion :
>> looks like the header is buggy, it should be "Digest":
>>> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
>
> The header is not buggy as 99.9% of SIP ABNF grammar is case
> insensitive. In fact the only case sensi
2010/6/17 Klaus Darilion :
> looks like the header is buggy, it should be "Digest":
>> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
The header is not buggy as 99.9% of SIP ABNF grammar is case
insensitive. In fact the only case sensitive are the SIP methods
(INVITE, REGIST
On Jun 17, 2010 at 16:39, David wrote:
> Hello,
>
> I had a look at RFC 3261, section 9.1. The trouble is that Kamailio
> is answering "100 Trying" to the caller, so the it is ok for the
> caller to send back a CANCEL request. Trouble is Kamailio forwards
> the request to the called user even tho
On 06/17/2010 04:46 PM, David wrote:
With my Cisco WIP310, what is happening is it is replying 481 Call
Leg/transaction unknown. After that it processes the INVITE
retransmission at which point it rings for 240 seconds. Which is a wee
bit annoying.
This is a very strange flow. If the caller s
Hey,
With my Cisco WIP310, what is happening is it is replying 481 Call
Leg/transaction unknown. After that it processes the INVITE
retransmission at which point it rings for 240 seconds. Which is a wee
bit annoying.
David
On 2010-06-17 16:43, Alex Balashov wrote:
David,
You can suppress
David,
You can suppress forwarding 100 Trying to the caller with the 0x01
flag to t_relay(). The problem is that then the caller will never
receive 100 Trying, as it is a "hop-by-hop" message; in other words,
when received from the callee, the proxy will not forward it.
Instead, the expecta
Hello,
I had a look at RFC 3261, section 9.1. The trouble is that Kamailio is
answering "100 Trying" to the caller, so the it is ok for the caller to
send back a CANCEL request. Trouble is Kamailio forwards the request to
the called user even though the called user never sent a provisional
re
Hey,
I am using a Cisco WIP310 wifi phone. Seeing as wifi is very battery
demanding, the phone goes into a standby mode. When it's in the standby
mode, it takes a few seconds to come back on.
So I send an INVITE to the phone, statefully using TM, I send out a
CANCEL before the phone returns
Hi Henning,
thanks for the follow-up. Seems like I am way too behind on all this.
"rewriting messages to the appropriate target...".. so how exactly does that
work ?
Geeze I wish I was a coder...
Thanks
lutz
-Ursprüngliche Nachricht-
Von: Henning Westerholt [mailto:henning.westerh...@1u
On Tuesday 15 June 2010, maybelater wrote:
> I am trying to set up the following:
> [..]
> 3. Connecting elastix/asterix to kamailio -> done
>
> I already have extensions configured on kamailio. They can call each other
> perfectly. Now I do need a route-config or dialplan that routes ALL
>
Am 17.06.2010 15:51, schrieb Ján ONDREJ (SAL):
WWW-Authenticate: DIGEST
realm="BroadWorks",qop="auth",algorithm=MD5,nonce="BroadWorksXgajlo4shTqsrkgdBW".
looks like the header is buggy, it should be "Digest":
> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
In module
Hello,
our voip provider requires autentication to voip services. Trying to use
UAC module, I get "401 Unauthorized" packet, but looks like all ser based
programs have problems to parse this packet. Can somebody make a patch to
fix this?
Here is message from logs:
Jun 17 15:01:42 kamailio /u
12 matches
Mail list logo
