Affects Version/s: None
Fix Version/s: None
On Fri, Aug 19, 2011 at 4:58 PM, M. Ranganathan <email@example.com> wrote:
Yes please open a JIRA issue. And if you post a diff (fix), I will
gratefully accept it and it will be faster (but please run the ant
torture target before submission).
On Fri, Aug 19, 2011 at 7:08 AM, Alper Ozdamar <firstname.lastname@example.org> wrote:
> Hello Ranga,
> Thank you for quick response. As you said, I upgraded my application's jain
> api to jain-sip-ri-1.2.1962.jar. But parser still ignores following header.
> P-Access-Network-Info: 3GPP-UTRAN-TDD;
> Parser doesn't like # and " characters. When I deleted these
> characters, P-Access-Network-Info header was parsed successfully.
> Then i read about P-Access-Network-Info header (RFC-3455 Private Header
> (P-Header) Extensions to the Session I) Rfc-3455 stated that our header
> parameters are allowable under the grammar. What should we do know ? Do you
> need bug report ?
> 5.4 P-Access-Network-Info header syntax
> The syntax of the P-Access-Network-Info header is described as
> P-Access-Network-Info = "P-Access-Network-Info" HCOLON
> access-net-spec = access-type *(SEMI access-info)
> access-type = "IEEE-802.11a" / "IEEE-802.11b" /
> "3GPP-GERAN" / "3GPP-UTRAN-FDD" /
> "3GPP-UTRAN-TDD" /
> "3GPP-CDMA2000" / token
> access-info = cgi-3gpp / utran-cell-id-3gpp /
> extension-access-info = gen-value
> cgi-3gpp = "cgi-3gpp" EQUAL
> (token / quoted-string)
> utran-cell-id-3gpp = "utran-cell-id-3gpp" EQUAL
> (token / quoted-string)
> The access-info may contain additional information relating to the
> access network. The values for "cgi-3gpp" and "utran-cell-id-3gpp"
> are defined in 3GPP TS 24.229 .
> Best Regards,
> Alper Ozdamar.
> On Thu, Aug 18, 2011 at 5:54 PM, M. Ranganathan <email@example.com> wrote:
>> Please upgrade to the latest version (you are way behind) and then
>> look at the P-Access-Network-Info header parser. Check the grammar for
>> that and make sure your header parameters are allowable under the
>> grammar. If they are fine, please post a bug report or a fix.
>> On Thu, Aug 18, 2011 at 9:48 AM, Alper Ozdamar <firstname.lastname@example.org>
>> > Hello,
>> > I'm having some problem while using Jain-sip-api-1.2. jar and
>> > jain-sip-ri-1.2.136.jar in my application. My application receives
>> > following
>> > registerMessage but after parsing sipMessage with StringMsgParser
>> > we are losing header which contains "ue-ip=18.104.22.168";"ue-port=50953"
>> > information.
>> > When i tried to parse same message with nist-sip-1.2.jar
>> > and JainSipApi1.2.jar, there were no problem.
>> > Do you have any suggestions ?
>> > REGISTER sip:turktelekom.com.tr SIP/2.0^M
>> > To: "11001"<sip:email@example.com:5060>^M
>> > From: "11001"<sip:firstname.lastname@example.org:5060>;tag=1^M
>> > Via: SIP/2.0/UDP
>> > 22.214.171.124:5060;branch=z9hG4bK-25412-1-0;received=126.96.36.199;rport=5060^M
>> > Call-ID: email@example.com^M
>> > CSeq: 1 REGISTER^M
>> > Contact: <sip:firstname.lastname@example.org:5060>^M
>> > Expires: 3600;
>> > P-Access-Network-Info: 3GPP-UTRAN-TDD;
>> > utran-cell-id-3gpp=#TTNET_PLAZA_LOCAL#;"ue-ip=188.8.131.52";"ue-port=50953"^M
>> > User-Agent: 11001^M
>> > Content-Length: 0^M
>> > Best Regards,
>> > Alper Ozdamar
>> > Software Engineer
>> M. Ranganathan