SIP REGISTER problem encountered in symbian build

AT
Alex T. W. LEUNG
Thu, Apr 17, 2008 7:54 AM

Hello,

The symbian_ua failed to register successfully. Instead, it returns:
pjsua_acc.c SIP registration error: Credential failed to authenticate
(PJSIP_EFAILEDCREDENTIAL [status=171100]

Both symbian_ua on emulator and symbian_ua on actual device (N82) will
see the same error. However, strangely, pjsua of release 0.8.0 can
register successfully on Windows, using the same sip credentials.

Here is the packet flow captured:
|Time    | 10.6.104.18      | proxy    |
|0.000    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 43983)
|        |(5060)  ------------------>  (5060)  |
|0.123    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0
bindings)
|        |(5060)  <------------------  (5060)  |
|0.503    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 43984)
|        |(5060)  ------------------>  (5060)  |
|0.591    |        Status: 200 OK    (          |SIP: Status: 200 OK
(1 bindings)
|        |(5060)  <------------------  (5060)  |
|0.887    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 43985)
|        |(5060)  ------------------>  (5060)  |
|0.981    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0
bindings)
|        |(5060)  <------------------  (5060)  |
|1.038    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 29318)
|        |(5060)  ------------------>  (5060)  |
|1.144    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0
bindings)
|        |(5060)  <------------------  (5060)  |
|1.384    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 43986)
|        |(5060)  ------------------>  (5060)  |
|1.482    |        Status: 200 OK    (          |SIP: Status: 200 OK
(0 bindings)
|        |(5060)  <------------------  (5060)  |
|1.718    |        Request: REGISTER s          |SIP: Request:
REGISTER sip:proxy (CSeq: 29319)
|        |(5060)  ------------------>  (5060)  |
|1.810    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - server-specified nonce should be uniquely generated    (0
bindings)
|        |(5060)  <------------------  (5060)  |

The above are facts gathered. I suspect that the error may be due to the
existence of REGISTER requests with strange CSeq number. In the above
capture, CSeq series of 43xxx seems to be normal. But the REGISTER with
CSeq 29xxx seems to be quite strange and unnecessary. By the way, pjsua
(rel 0.8.0) on Windows don't generate these kind of strange CSeq series
in the REGISTER process.

Thank you for shedding some lights on this issue! Wish you all a good
day.

Alex Leung.

This message (including any attachments) is for the named
addressee(s)'s use only. It may contain sensitive, confidential,
private proprietary or legally privileged information intended for a
specific individual and purpose, and is protected by law. If you are
not the intended recipient, please immediately delete it and all copies
of it from your system, destroy any hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of
this message and/or any attachments is strictly prohibited.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





Hello, The symbian_ua failed to register successfully. Instead, it returns: pjsua_acc.c SIP registration error: Credential failed to authenticate (PJSIP_EFAILEDCREDENTIAL [status=171100] Both symbian_ua on emulator and symbian_ua on actual device (N82) will see the same error. However, strangely, pjsua of release 0.8.0 can register successfully on Windows, using the same sip credentials. Here is the packet flow captured: |Time | 10.6.104.18 | proxy | |0.000 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 43983) | |(5060) ------------------> (5060) | |0.123 | Status: 401 Unautho |SIP: Status: 401 Unauthorized - no credentials are provided in the request (0 bindings) | |(5060) <------------------ (5060) | |0.503 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 43984) | |(5060) ------------------> (5060) | |0.591 | Status: 200 OK ( |SIP: Status: 200 OK (1 bindings) | |(5060) <------------------ (5060) | |0.887 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 43985) | |(5060) ------------------> (5060) | |0.981 | Status: 401 Unautho |SIP: Status: 401 Unauthorized - no credentials are provided in the request (0 bindings) | |(5060) <------------------ (5060) | |1.038 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 29318) | |(5060) ------------------> (5060) | |1.144 | Status: 401 Unautho |SIP: Status: 401 Unauthorized - no credentials are provided in the request (0 bindings) | |(5060) <------------------ (5060) | |1.384 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 43986) | |(5060) ------------------> (5060) | |1.482 | Status: 200 OK ( |SIP: Status: 200 OK (0 bindings) | |(5060) <------------------ (5060) | |1.718 | Request: REGISTER s |SIP: Request: REGISTER sip:proxy (CSeq: 29319) | |(5060) ------------------> (5060) | |1.810 | Status: 401 Unautho |SIP: Status: 401 Unauthorized - server-specified nonce should be uniquely generated (0 bindings) | |(5060) <------------------ (5060) | The above are facts gathered. I suspect that the error may be due to the existence of REGISTER requests with strange CSeq number. In the above capture, CSeq series of 43xxx seems to be normal. But the REGISTER with CSeq 29xxx seems to be quite strange and unnecessary. By the way, pjsua (rel 0.8.0) on Windows don't generate these kind of strange CSeq series in the REGISTER process. Thank you for shedding some lights on this issue! Wish you all a good day. Alex Leung. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BP
Benny Prijono
Sat, Apr 19, 2008 12:29 PM

On Thu, Apr 17, 2008 at 3:54 AM, Alex T. W. LEUNG alexleung@astri.org wrote:

Hello,

The symbian_ua failed to register successfully. Instead, it returns:

pjsua_acc.c SIP registration error: Credential failed to authenticate
(PJSIP_EFAILEDCREDENTIAL [status=171100]

Both symbian_ua on emulator and symbian_ua on actual device (N82) will see
the same error. However, strangely, pjsua of release 0.8.0 can register
successfully on Windows, using the same sip credentials.

Here is the packet flow captured:
|Time    | 10.6.104.18      | proxy    |
|0.000    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 43983)
|        |(5060)  ------------------>  (5060)  |
|0.123    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0 bindings)
|        |(5060)  <------------------  (5060)  |
|0.503    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 43984)
|        |(5060)  ------------------>  (5060)  |
|0.591    |        Status: 200 OK    (          |SIP: Status: 200 OK    (1
bindings)
|        |(5060)  <------------------  (5060)  |
|0.887    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 43985)
|        |(5060)  ------------------>  (5060)  |
|0.981    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0 bindings)
|        |(5060)  <------------------  (5060)  |
|1.038    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 29318)
|        |(5060)  ------------------>  (5060)  |
|1.144    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - no credentials are provided in the request    (0 bindings)
|        |(5060)  <------------------  (5060)  |
|1.384    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 43986)
|        |(5060)  ------------------>  (5060)  |
|1.482    |        Status: 200 OK    (          |SIP: Status: 200 OK    (0
bindings)
|        |(5060)  <------------------  (5060)  |
|1.718    |        Request: REGISTER s          |SIP: Request: REGISTER
sip:proxy (CSeq: 29319)
|        |(5060)  ------------------>  (5060)  |
|1.810    |        Status: 401 Unautho          |SIP: Status: 401
Unauthorized - server-specified nonce should be uniquely generated    (0
bindings)
|        |(5060)  <------------------  (5060)  |

The above are facts gathered. I suspect that the error may be due to the
existence of REGISTER requests with strange CSeq number. In the above
capture, CSeq series of 43xxx seems to be normal. But the REGISTER with CSeq
29xxx seems to be quite strange and unnecessary. By the way, pjsua (rel
0.8.0) on Windows don't generate these kind of strange CSeq series in the
REGISTER process.

Hi Alex,

Since release 0.8.0, we have a feature to automatically update the
registration if the Contact address is different than the Via
received/rport value. Have a look at
http://trac.pjsip.org/repos/ticket/381

This works fine with most servers so far, and it should. Could it be
that your server doesn't like this?

Cheers
Benny

Thank you for shedding some lights on this issue! Wish you all a good day.

Alex Leung.

On Thu, Apr 17, 2008 at 3:54 AM, Alex T. W. LEUNG <alexleung@astri.org> wrote: > > > Hello, > > The symbian_ua failed to register successfully. Instead, it returns: > > pjsua_acc.c SIP registration error: Credential failed to authenticate > (PJSIP_EFAILEDCREDENTIAL [status=171100] > > Both symbian_ua on emulator and symbian_ua on actual device (N82) will see > the same error. However, strangely, pjsua of release 0.8.0 can register > successfully on Windows, using the same sip credentials. > > Here is the packet flow captured: > |Time | 10.6.104.18 | proxy | > |0.000 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 43983) > | |(5060) ------------------> (5060) | > |0.123 | Status: 401 Unautho |SIP: Status: 401 > Unauthorized - no credentials are provided in the request (0 bindings) > | |(5060) <------------------ (5060) | > |0.503 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 43984) > | |(5060) ------------------> (5060) | > |0.591 | Status: 200 OK ( |SIP: Status: 200 OK (1 > bindings) > | |(5060) <------------------ (5060) | > |0.887 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 43985) > | |(5060) ------------------> (5060) | > |0.981 | Status: 401 Unautho |SIP: Status: 401 > Unauthorized - no credentials are provided in the request (0 bindings) > | |(5060) <------------------ (5060) | > |1.038 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 29318) > | |(5060) ------------------> (5060) | > |1.144 | Status: 401 Unautho |SIP: Status: 401 > Unauthorized - no credentials are provided in the request (0 bindings) > | |(5060) <------------------ (5060) | > |1.384 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 43986) > | |(5060) ------------------> (5060) | > |1.482 | Status: 200 OK ( |SIP: Status: 200 OK (0 > bindings) > | |(5060) <------------------ (5060) | > |1.718 | Request: REGISTER s |SIP: Request: REGISTER > sip:proxy (CSeq: 29319) > | |(5060) ------------------> (5060) | > |1.810 | Status: 401 Unautho |SIP: Status: 401 > Unauthorized - server-specified nonce should be uniquely generated (0 > bindings) > | |(5060) <------------------ (5060) | > > The above are facts gathered. I suspect that the error may be due to the > existence of REGISTER requests with strange CSeq number. In the above > capture, CSeq series of 43xxx seems to be normal. But the REGISTER with CSeq > 29xxx seems to be quite strange and unnecessary. By the way, pjsua (rel > 0.8.0) on Windows don't generate these kind of strange CSeq series in the > REGISTER process. Hi Alex, Since release 0.8.0, we have a feature to automatically update the registration if the Contact address is different than the Via received/rport value. Have a look at http://trac.pjsip.org/repos/ticket/381 This works fine with most servers so far, and it should. Could it be that your server doesn't like this? Cheers Benny > Thank you for shedding some lights on this issue! Wish you all a good day. > > Alex Leung. >
RK
Roland Klabunde
Sat, Apr 19, 2008 8:56 PM

Hi (Benny),

Martin (!) has built the wince sample of the latest SVN, switched off VAD
and EC and got hmmmm..... some sort of a walky talky :) Means: The audio was
half-duplex only. Only if one side was silent, the other's audio came
through. ASUS PDA. From this device we know, that the GSM audio quality is
horrible, but was at least full duplex. PTIME is 20, no change with PTIME
80.

Is there anything known about this issue? I haven't double checked his
settings, so I just rely on his reports (and my ears too of course :))

Regards

Hi (Benny), Martin (!) has built the wince sample of the latest SVN, switched off VAD and EC and got hmmmm..... some sort of a walky talky :) Means: The audio was half-duplex only. Only if one side was silent, the other's audio came through. ASUS PDA. From this device we know, that the GSM audio quality is horrible, but was at least full duplex. PTIME is 20, no change with PTIME 80. Is there anything known about this issue? I haven't double checked his settings, so I just rely on his reports (and my ears too of course :)) Regards
BP
Benny Prijono
Sun, Apr 20, 2008 11:27 AM

On Sat, Apr 19, 2008 at 4:56 PM, Roland Klabunde
roland.klabunde@freenet.de wrote:

Hi (Benny),

Martin (!) has built the wince sample of the latest SVN, switched off VAD
and EC and got hmmmm..... some sort of a walky talky :) Means: The audio was
half-duplex only. Only if one side was silent, the other's audio came
through. ASUS PDA. From this device we know, that the GSM audio quality is
horrible, but was at least full duplex. PTIME is 20, no change with PTIME
80.

That sounds like the echo suppressor (PJMEDIA_ECHO_SIMPLE) is in
operation. So the EC is not totally disabled after all. In PJSUA-LIB
you can disable the EC by setting the ec_tail to zero.

Cheers
Benny

Is there anything known about this issue? I haven't double checked his
settings, so I just rely on his reports (and my ears too of course :))

Regards


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

On Sat, Apr 19, 2008 at 4:56 PM, Roland Klabunde <roland.klabunde@freenet.de> wrote: > Hi (Benny), > > Martin (!) has built the wince sample of the latest SVN, switched off VAD > and EC and got hmmmm..... some sort of a walky talky :) Means: The audio was > half-duplex only. Only if one side was silent, the other's audio came > through. ASUS PDA. From this device we know, that the GSM audio quality is > horrible, but was at least full duplex. PTIME is 20, no change with PTIME > 80. That sounds like the echo suppressor (PJMEDIA_ECHO_SIMPLE) is in operation. So the EC is not totally disabled after all. In PJSUA-LIB you can disable the EC by setting the ec_tail to zero. Cheers Benny > Is there anything known about this issue? I haven't double checked his > settings, so I just rely on his reports (and my ears too of course :)) > > Regards > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
RK
Roland Klabunde
Sun, Apr 20, 2008 11:36 AM

Yes, Martin swear's, he did it already :)

But let's see.

Other possible things?

Regards

----- Original Message -----
From: "Benny Prijono" bennylp@pjsip.org
To: "pjsip list" pjsip@lists.pjsip.org
Sent: Sunday, April 20, 2008 1:27 PM
Subject: Re: [pjsip] Windows Mobile 6 half duplex audio - anything known?

On Sat, Apr 19, 2008 at 4:56 PM, Roland Klabunde
roland.klabunde@freenet.de wrote:

Hi (Benny),

Martin has built the wince sample of the latest SVN, switched off VAD
and EC and got hmmmm..... some sort of a walky talky :) Means: The audio
was
half-duplex only. Only if one side was silent, the other's audio came
through. ASUS PDA. From this device we know, that the GSM audio quality
is
horrible, but was at least full duplex. PTIME is 20, no change with
PTIME
80.

That sounds like the echo suppressor (PJMEDIA_ECHO_SIMPLE) is in
operation. So the EC is not totally disabled after all. In PJSUA-LIB
you can disable the EC by setting the ec_tail to zero.

Cheers
Benny

Is there anything known about this issue? I haven't double checked his
settings, so I just rely on his reports (and my ears too of course :))

Regards


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

Yes, Martin swear's, he did it already :) But let's see. Other possible things? Regards ----- Original Message ----- From: "Benny Prijono" <bennylp@pjsip.org> To: "pjsip list" <pjsip@lists.pjsip.org> Sent: Sunday, April 20, 2008 1:27 PM Subject: Re: [pjsip] Windows Mobile 6 half duplex audio - anything known? > On Sat, Apr 19, 2008 at 4:56 PM, Roland Klabunde > <roland.klabunde@freenet.de> wrote: >> Hi (Benny), >> >> Martin has built the wince sample of the latest SVN, switched off VAD >> and EC and got hmmmm..... some sort of a walky talky :) Means: The audio >> was >> half-duplex only. Only if one side was silent, the other's audio came >> through. ASUS PDA. From this device we know, that the GSM audio quality >> is >> horrible, but was at least full duplex. PTIME is 20, no change with >> PTIME >> 80. > > That sounds like the echo suppressor (PJMEDIA_ECHO_SIMPLE) is in > operation. So the EC is not totally disabled after all. In PJSUA-LIB > you can disable the EC by setting the ec_tail to zero. > > Cheers > Benny > >> Is there anything known about this issue? I haven't double checked his >> settings, so I just rely on his reports (and my ears too of course :)) >> >> Regards >> >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
BP
Benny Prijono
Sun, Apr 20, 2008 11:45 AM

On Sun, Apr 20, 2008 at 7:36 AM, Roland Klabunde
roland.klabunde@freenet.de wrote:

Yes, Martin swear's, he did it already :)

But let's see.

Other possible things?

I can't think of anything else. But what you described sounds exactly
like the work of the echo suppressor.

Cheers
Benny

On Sun, Apr 20, 2008 at 7:36 AM, Roland Klabunde <roland.klabunde@freenet.de> wrote: > Yes, Martin swear's, he did it already :) > > But let's see. > > Other possible things? > I can't think of anything else. But what you described sounds exactly like the work of the echo suppressor. Cheers Benny
AT
Alex T. W. LEUNG
Mon, Apr 21, 2008 7:12 AM

Dear Benny,

You advice is very helpful. I add the below line to ua.cpp:
cfg.allow_contact_rewrite = PJ_FALSE;

This disables the registration update due to contact being different
from ip-addr/port values in Via. Thanks so much.

Alex.

-----Original Message-----
From: pjsip-bounces@lists.pjsip.org
[mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Benny Prijono
Sent: Saturday, April 19, 2008 8:30 PM
To: pjsip list
Subject: Re: [pjsip] SIP REGISTER problem encountered in symbian build

On Thu, Apr 17, 2008 at 3:54 AM, Alex T. W. LEUNG alexleung@astri.org
wrote:

Hello,

The symbian_ua failed to register successfully. Instead, it returns:

pjsua_acc.c SIP registration error: Credential failed to authenticate
(PJSIP_EFAILEDCREDENTIAL [status=171100]

Both symbian_ua on emulator and symbian_ua on actual device (N82) will

see the same error. However, strangely, pjsua of release 0.8.0 can
register successfully on Windows, using the same sip credentials.

......

The above are facts gathered. I suspect that the error may be due to
the existence of REGISTER requests with strange CSeq number. In the
above capture, CSeq series of 43xxx seems to be normal. But the
REGISTER with CSeq 29xxx seems to be quite strange and unnecessary. By

the way, pjsua (rel
0.8.0) on Windows don't generate these kind of strange CSeq series in

the

REGISTER process.

Hi Alex,

Since release 0.8.0, we have a feature to automatically update the
registration if the Contact address is different than the Via
received/rport value. Have a look at
http://trac.pjsip.org/repos/ticket/381

This works fine with most servers so far, and it should. Could it be
that your server doesn't like this?

Cheers
Benny

Thank you for shedding some lights on this issue! Wish you all a good
day.

Alex Leung.


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

This message (including any attachments) is for the named
addressee(s)'s use only. It may contain sensitive, confidential,
private proprietary or legally privileged information intended for a
specific individual and purpose, and is protected by law. If you are
not the intended recipient, please immediately delete it and all copies
of it from your system, destroy any hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of
this message and/or any attachments is strictly prohibited.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Dear Benny, You advice is very helpful. I add the below line to ua.cpp: cfg.allow_contact_rewrite = PJ_FALSE; This disables the registration update due to contact being different from ip-addr/port values in Via. Thanks so much. Alex. -----Original Message----- From: pjsip-bounces@lists.pjsip.org [mailto:pjsip-bounces@lists.pjsip.org] On Behalf Of Benny Prijono Sent: Saturday, April 19, 2008 8:30 PM To: pjsip list Subject: Re: [pjsip] SIP REGISTER problem encountered in symbian build On Thu, Apr 17, 2008 at 3:54 AM, Alex T. W. LEUNG <alexleung@astri.org> wrote: > > > Hello, > > The symbian_ua failed to register successfully. Instead, it returns: > > pjsua_acc.c SIP registration error: Credential failed to authenticate > (PJSIP_EFAILEDCREDENTIAL [status=171100] > > Both symbian_ua on emulator and symbian_ua on actual device (N82) will > see the same error. However, strangely, pjsua of release 0.8.0 can > register successfully on Windows, using the same sip credentials. > ...... > > The above are facts gathered. I suspect that the error may be due to > the existence of REGISTER requests with strange CSeq number. In the > above capture, CSeq series of 43xxx seems to be normal. But the > REGISTER with CSeq 29xxx seems to be quite strange and unnecessary. By > the way, pjsua (rel > 0.8.0) on Windows don't generate these kind of strange CSeq series in the > REGISTER process. Hi Alex, Since release 0.8.0, we have a feature to automatically update the registration if the Contact address is different than the Via received/rport value. Have a look at http://trac.pjsip.org/repos/ticket/381 This works fine with most servers so far, and it should. Could it be that your server doesn't like this? Cheers Benny > Thank you for shedding some lights on this issue! Wish you all a good > day. > > Alex Leung. > _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~