RFC5626 non-standard behaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RFC5626 non-standard behaviour
From: nanang@xxxxxxxxx (Nanang Izzuddin)
Date: Tue, 11 Oct 2011 14:33:08 +0700
In-reply-to: <CAN6v_a-Uhvuy0LgwBEZdavkXLDX3HAuGx05NvBLZuvhZLHUbKw@mail.gmail.com>

Hi Gustavo,

Regarding the assertion, I can't reproduce it here. Instead, found a
bug in pjsip_endpt_send_raw_to_uri() which doesn't seem to be related,
see https://trac.pjsip.org/repos/ticket/1386.

BR,
nanang

References:
- RFC5626 non-standard behaviour
  - From: Gustavo Garcia Bernardo
- RFC5626 non-standard behaviour
  - From: Benny Prijono
- RFC5626 non-standard behaviour
  - From: Gustavo Garcia Bernardo
- RFC5626 non-standard behaviour
  - From: Benny Prijono
- RFC5626 non-standard behaviour
  - From: Gustavo
- RFC5626 non-standard behaviour
  - From: Benny Prijono

Prev by Date: Microsoft C# Compatible
Next by Date: Problem using TCP as transport with ";transport=tcp"
Previous by thread: RFC5626 non-standard behaviour
Next by thread: How to disable codec lock using pjsua
Index(es):
- Date
- Thread

[Index of Archives] [Asterisk Users] [Asterisk App Development] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [Linux API]

Powered by Linux