[sip-comm-dev] green SIP button & some questions


#1

Dear All,
few short questions:
1) if my SC is switched on continously I can only see if another SIP buddy
is online if he/she is online in parallel with an e.g. jabber-account - or
I turn off/on my SC regularly - correct? (otherwise I see only grey buttons,
if I dont restart SC to "update" this view)

2) does SIP-chat support OTR encryption? (at least it is not working on my
SC)

3) should Video-zRTP already work? If yes: could somebody test between SC
windows versions for that (so far all my attempts have failed to make video
calls between two iptel accounts).
if not: I will wait patiently...

will be happy for short in-line answers!

kind regards, MS


#2

Hello Mr Smith,

Mr Smith написа:

Dear All,
few short questions:
1) if my SC is switched on continously I can only see if another SIP
buddy is online if he/she is online in parallel with an e.g.
jabber-account - or I turn off/on my SC regularly - correct?

Actually not. Presence is supposed to work for SIP. Make sure you enable
the support for a presence agent when creating an account or enable it
later on. If that's not working for your then we need to see a wireshark
dump and try to fix it.

(otherwise
I see only grey buttons, if I dont restart SC to "update" this view)

2) does SIP-chat support OTR encryption? (at least it is not working on
my SC)

OTR encryption is not currently implemented for our protocol provider.
There's no technical reason that prevents us from implementing it
though. It's all a matter of finding the time or someone contributing this.

3) should Video-zRTP already work?

Yes.

If yes: could somebody test between
SC windows versions for that (so far all my attempts have failed to make
video calls between two iptel accounts).
if not: I will wait patiently...

There's a problem with video on iptel.org right now. We have reported
the problem and are waiting for someone on their side to look into it.
Will report on this list when this happens.

Cheers,
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hello Emil,
thanks for the answer!
maybe I mix here up something: when I was testing with Werner about the
topic of the "green SIP button" you mentioned afterwards the problems with
NOTIFY/SUBSCRIBE.
I am using both iptel and sipphone (in both accounts the options "enable
presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are checked)
however my partners do not see me online and vice-versa; sometimes only
after restarting SC; sometimes the green button turns to grey although we
both stay online.
Are the settings correct?

kind regards, MS

···

2010/1/23 Emil Ivov <emcho@sip-communicator.org>

Hello Mr Smith,

Mr Smith написа:
> Dear All,
> few short questions:
> 1) if my SC is switched on continously I can only see if another SIP
> buddy is online if he/she is online in parallel with an e.g.
> jabber-account - or I turn off/on my SC regularly - correct?

Actually not. Presence is supposed to work for SIP. Make sure you enable
the support for a presence agent when creating an account or enable it
later on. If that's not working for your then we need to see a wireshark
dump and try to fix it.

> (otherwise
> I see only grey buttons, if I dont restart SC to "update" this view)
>
> 2) does SIP-chat support OTR encryption? (at least it is not working on
> my SC)

OTR encryption is not currently implemented for our protocol provider.
There's no technical reason that prevents us from implementing it
though. It's all a matter of finding the time or someone contributing this.

> 3) should Video-zRTP already work?

Yes.

> If yes: could somebody test between
> SC windows versions for that (so far all my attempts have failed to make
> video calls between two iptel accounts).
> if not: I will wait patiently...

There's a problem with video on iptel.org right now. We have reported
the problem and are waiting for someone on their side to look into it.
Will report on this list when this happens.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hey MS,

Mr Smith написа:

Hello Emil,
thanks for the answer!
maybe I mix here up something: when I was testing with Werner about the
topic of the "green SIP button" you mentioned afterwards the problems
with NOTIFY/SUBSCRIBE.
I am using both iptel and sipphone (in both accounts the options "enable
presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are checked)
however my partners do not see me online and vice-versa; sometimes only
after restarting SC; sometimes the green button turns to grey although
we both stay online.
Are the settings correct?

You should unchecking the "Force peer-to-peer presence mode" option so
that SC would use the server as a presence agent.

Let me know how it goes.

Cheers,
Emil

···

kind regards, MS

2010/1/23 Emil Ivov <emcho@sip-communicator.org
<mailto:emcho@sip-communicator.org>>

    Hello Mr Smith,

    Mr Smith написа:
    > Dear All,
    > few short questions:
    > 1) if my SC is switched on continously I can only see if another SIP
    > buddy is online if he/she is online in parallel with an e.g.
    > jabber-account - or I turn off/on my SC regularly - correct?

    Actually not. Presence is supposed to work for SIP. Make sure you enable
    the support for a presence agent when creating an account or enable it
    later on. If that's not working for your then we need to see a wireshark
    dump and try to fix it.

    > (otherwise
    > I see only grey buttons, if I dont restart SC to "update" this view)
    >
    > 2) does SIP-chat support OTR encryption? (at least it is not
    working on
    > my SC)

    OTR encryption is not currently implemented for our protocol provider.
    There's no technical reason that prevents us from implementing it
    though. It's all a matter of finding the time or someone
    contributing this.

    > 3) should Video-zRTP already work?

    Yes.

    > If yes: could somebody test between
    > SC windows versions for that (so far all my attempts have failed
    to make
    > video calls between two iptel accounts).
    > if not: I will wait patiently...

    There's a problem with video on iptel.org <http://iptel.org> right
    now. We have reported
    the problem and are waiting for someone on their side to look into it.
    Will report on this list when this happens.

    Cheers,
    Emil

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hello Emil,
I tried now with the iptel account (sipphone had unstable connection):
no change in the colour of the presence-button on the SIP account after
unchecking "force-peer-to-peer-presence" on both sides:
on my labtop my buddy was shown green, he saw me only "grey/offline" (we
both did not restart SC again)

Interesting: I could phone (only audio-call with zrtp) him , the secure
connection took place but I could not hear him (he could hear me with
"excellent quality".)
If he phoned me I was not able to accept his call (the receiver-button did
not react), sometimes a new call-window appeared from him even the first did
not close.
(maybe I am not able to describe more clear what I experienced).

We both use latest win-version (nb 2364) with default settings for audio.
The headsets are ok because we tried before/afterwards with skype

Kind regards, MS

···

2010/1/23 Emil Ivov <emcho@sip-communicator.org>

Hey MS,

Mr Smith написа:
> Hello Emil,
> thanks for the answer!
> maybe I mix here up something: when I was testing with Werner about the
> topic of the "green SIP button" you mentioned afterwards the problems
> with NOTIFY/SUBSCRIBE.
> I am using both iptel and sipphone (in both accounts the options "enable
> presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are checked)
> however my partners do not see me online and vice-versa; sometimes only
> after restarting SC; sometimes the green button turns to grey although
> we both stay online.
> Are the settings correct?

You should unchecking the "Force peer-to-peer presence mode" option so
that SC would use the server as a presence agent.

Let me know how it goes.

Cheers,
Emil

>
> kind regards, MS
>
> 2010/1/23 Emil Ivov <emcho@sip-communicator.org
> <mailto:emcho@sip-communicator.org>>
>
> Hello Mr Smith,
>
> Mr Smith написа:
> > Dear All,
> > few short questions:
> > 1) if my SC is switched on continously I can only see if another
SIP
> > buddy is online if he/she is online in parallel with an e.g.
> > jabber-account - or I turn off/on my SC regularly - correct?
>
> Actually not. Presence is supposed to work for SIP. Make sure you
enable
> the support for a presence agent when creating an account or enable
it
> later on. If that's not working for your then we need to see a
wireshark
> dump and try to fix it.
>
> > (otherwise
> > I see only grey buttons, if I dont restart SC to "update" this
view)
> >
> > 2) does SIP-chat support OTR encryption? (at least it is not
> working on
> > my SC)
>
> OTR encryption is not currently implemented for our protocol
provider.
> There's no technical reason that prevents us from implementing it
> though. It's all a matter of finding the time or someone
> contributing this.
>
> > 3) should Video-zRTP already work?
>
> Yes.
>
> > If yes: could somebody test between
> > SC windows versions for that (so far all my attempts have failed
> to make
> > video calls between two iptel accounts).
> > if not: I will wait patiently...
>
> There's a problem with video on iptel.org <http://iptel.org> right
> now. We have reported
> the problem and are waiting for someone on their side to look into
it.
> Will report on this list when this happens.
>
> Cheers,
> Emil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@sip-communicator.dev.java.net
> <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
> For additional commands, e-mail:
> dev-help@sip-communicator.dev.java.net
> <mailto:dev-help@sip-communicator.dev.java.net>
>
>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi Mr. Smith,

I opened up two test accounts for you on my personal SIP server and
sent you access details via email. I would like to know your test results
of green presence indicator and whether you have 2-way audio?.

Regards, Earl

Mr Smith wrote:

···

Hello Emil,
I tried now with the iptel account (sipphone had unstable connection):
no change in the colour of the presence-button on the SIP account after unchecking "force-peer-to-peer-presence" on both sides:
on my labtop my buddy was shown green, he saw me only "grey/offline" (we both did not restart SC again)

Interesting: I could phone (only audio-call with zrtp) him , the secure connection took place but I could not hear him (he could hear me with "excellent quality".)
If he phoned me I was not able to accept his call (the receiver-button did not react), sometimes a new call-window appeared from him even the first did not close.
(maybe I am not able to describe more clear what I experienced).

We both use latest win-version (nb 2364) with default settings for audio. The headsets are ok because we tried before/afterwards with skype

Kind regards, MS

2010/1/23 Emil Ivov <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>>

    Hey MS,

    Mr Smith написа:
    > Hello Emil,
    > thanks for the answer!
    > maybe I mix here up something: when I was testing with Werner
    about the
    > topic of the "green SIP button" you mentioned afterwards the
    problems
    > with NOTIFY/SUBSCRIBE.
    > I am using both iptel and sipphone (in both accounts the options
    "enable
    > presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are
    checked)
    > however my partners do not see me online and vice-versa;
    sometimes only
    > after restarting SC; sometimes the green button turns to grey
    although
    > we both stay online.
    > Are the settings correct?

    You should unchecking the "Force peer-to-peer presence mode" option so
    that SC would use the server as a presence agent.

    Let me know how it goes.

    Cheers,
    Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

I see Mr. Smith logged into my server, which is on the same LAN as
myself (MilkFish server openSER embedded). I am also registered.
SIP server is in a LinkSys router, reflashed to DD-WRT v.2.4SP1
O/S.

I added Mr. Smith as a contact, but do not see him green. When I
tried to send him a SIP msg, I got an error report. Interesting that
my Send Via icon says SIP off, even though I see that I am registered
in the server.

Will try from other LAN stations and see if there is a difference.
Will look at the server SIP trace, and later will install pcap and
wireshark.

Earl

Earl wrote:

···

Hi Mr. Smith,

I opened up two test accounts for you on my personal SIP server and
sent you access details via email. I would like to know your test results
of green presence indicator and whether you have 2-way audio?.

Regards, Earl

Mr Smith wrote:

Hello Emil,
I tried now with the iptel account (sipphone had unstable connection):
no change in the colour of the presence-button on the SIP account after unchecking "force-peer-to-peer-presence" on both sides:
on my labtop my buddy was shown green, he saw me only "grey/offline" (we both did not restart SC again)

Interesting: I could phone (only audio-call with zrtp) him , the secure connection took place but I could not hear him (he could hear me with "excellent quality".)
If he phoned me I was not able to accept his call (the receiver-button did not react), sometimes a new call-window appeared from him even the first did not close.
(maybe I am not able to describe more clear what I experienced).

We both use latest win-version (nb 2364) with default settings for audio. The headsets are ok because we tried before/afterwards with skype

Kind regards, MS

2010/1/23 Emil Ivov <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>>

    Hey MS,

    Mr Smith написа:
    > Hello Emil,
    > thanks for the answer!
    > maybe I mix here up something: when I was testing with Werner
    about the
    > topic of the "green SIP button" you mentioned afterwards the
    problems
    > with NOTIFY/SUBSCRIBE.
    > I am using both iptel and sipphone (in both accounts the options
    "enable
    > presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are
    checked)
    > however my partners do not see me online and vice-versa;
    sometimes only
    > after restarting SC; sometimes the green button turns to grey
    although
    > we both stay online.
    > Are the settings correct?

    You should unchecking the "Force peer-to-peer presence mode" option so
    that SC would use the server as a presence agent.

    Let me know how it goes.

    Cheers,
    Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

One more comment. When I click on the down arrow at the top
of the main SC window, I see a green SIP on icon.
But in a SIP chat window the Send Via says SIP off gray.
The SIP server confirms both users registered.

Also the account window has me logged in with green SIP

···

ON icon. Earl Earl wrote:

I see Mr. Smith logged into my server, which is on the same LAN as
myself (MilkFish server openSER embedded). I am also registered.
SIP server is in a LinkSys router, reflashed to DD-WRT v.2.4SP1
O/S.

I added Mr. Smith as a contact, but do not see him green. When I
tried to send him a SIP msg, I got an error report. Interesting that
my Send Via icon says SIP off, even though I see that I am registered
in the server.

Will try from other LAN stations and see if there is a difference.
Will look at the server SIP trace, and later will install pcap and
wireshark.

Earl

Earl wrote:

Hi Mr. Smith,

I opened up two test accounts for you on my personal SIP server and
sent you access details via email. I would like to know your test results
of green presence indicator and whether you have 2-way audio?.

Regards, Earl

Mr Smith wrote:

Hello Emil,
I tried now with the iptel account (sipphone had unstable connection):
no change in the colour of the presence-button on the SIP account after unchecking "force-peer-to-peer-presence" on both sides:
on my labtop my buddy was shown green, he saw me only "grey/offline" (we both did not restart SC again)

Interesting: I could phone (only audio-call with zrtp) him , the secure connection took place but I could not hear him (he could hear me with "excellent quality".)
If he phoned me I was not able to accept his call (the receiver-button did not react), sometimes a new call-window appeared from him even the first did not close.
(maybe I am not able to describe more clear what I experienced).

We both use latest win-version (nb 2364) with default settings for audio. The headsets are ok because we tried before/afterwards with skype

Kind regards, MS

2010/1/23 Emil Ivov <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>>

    Hey MS,

    Mr Smith написа:
    > Hello Emil,
    > thanks for the answer!
    > maybe I mix here up something: when I was testing with Werner
    about the
    > topic of the "green SIP button" you mentioned afterwards the
    problems
    > with NOTIFY/SUBSCRIBE.
    > I am using both iptel and sipphone (in both accounts the options
    "enable
    > presence (SIMPLE)" and "force-peer-to-peer-presence-mode" are
    checked)
    > however my partners do not see me online and vice-versa;
    sometimes only
    > after restarting SC; sometimes the green button turns to grey
    although
    > we both stay online.
    > Are the settings correct?

    You should unchecking the "Force peer-to-peer presence mode" option so
    that SC would use the server as a presence agent.

    Let me know how it goes.

    Cheers,
    Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

We are both using build 2366.

Earl wrote:

···

One more comment. When I click on the down arrow at the top
of the main SC window, I see a green SIP on icon.
But in a SIP chat window the Send Via says SIP off gray.
The SIP server confirms both users registered.

Also the account window has me logged in with green SIP
ON icon. > > Earl > > Earl wrote:

I see Mr. Smith logged into my server, which is on the same LAN as
myself (MilkFish server openSER embedded). I am also registered.
SIP server is in a LinkSys router, reflashed to DD-WRT v.2.4SP1
O/S.

I added Mr. Smith as a contact, but do not see him green. When I
tried to send him a SIP msg, I got an error report. Interesting that
my Send Via icon says SIP off, even though I see that I am registered
in the server.

Will try from other LAN stations and see if there is a difference.
Will look at the server SIP trace, and later will install pcap and
wireshark.

Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

I confirm on 3 computers on my LAN, that none see Mr. Smith as green.
None have green SIP ON icon for Send Via, all have gray OFF.
All are registered in the SIP server.
Here is the SIP server trace. I noticed that some of the FROM: and
This embedded SIP server tests if connections are in same LAN
so it can route them LAN-LAN instead of over Inet.
Notice that it is possible that the problem is in my SIP server ???
Which is why I must install pcap and wireshark.

In spite of SIP msg window having gray SIP OFF Send Via, I can
still SIP message here between LAN computers. However, SIP
msg to Mr Smith does not work and returns error report: 408 request
timeout.

I just noticed the appearance of a new roster contact from Claudia-4
under "not in contact list" group, which has green circle. She has
another appearance in the roster with different roster name that is gray.
I did not create the new roster entry except perhaps as replying to a
msg from SC about accepting her request.
I deleted the original contact entry that I manually entered via menus
and the newly generated contact remained and is green.

The same thing happened on Claudia-4's computer. The original roster
entry for Earl is still gray presence, but there is a newly generated one
under "not in contact list" group that is green. What generated this new
green entry, I am not sure. For sure, I did not manually generate this
contact using menus. It must have been generated by SC automatically
perhaps as a result of some manipulation that I did. I kind of remember
clicking on a accept/reject pop-up, replying accept. I thought this only
happened for Jabber ???

I will close the SIP trace window and open it again and send the contents
in a new post, now that I see green. Between Earl and Claudia, there is
still NO green SIP presence.

SIP Trace
Close and open this window again to update trace...
note: I have replaced my numeric public IP with a phrase

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 520 REGISTER

From: ;tag=40828900

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK7cbebc6c7ccf520c977bfd95ad26ca7f
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 270 REGISTER

From: ;tag=3e503cbd

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bKc23bf228b916d6713b24dc026a059000
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 193 REGISTER

From: ;tag=7576ed4a

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bKa49656b87125ce66e9da3f58e7404fca
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 519 REGISTER

From: ;tag=23ad6c58

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bKf90c59b2bcff1bf5480c874c073ac829
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 269 REGISTER

From: ;tag=dce00959

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bKe5eb2a0bc3b33ca18798e37f28a6fd8d
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 192 REGISTER

From: ;tag=ec40b8a4

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK5e7d7be12654bdce0e4799ea3b0d42f0
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 518 REGISTER

From: ;tag=53a80fed

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK61123bbf59d497f013e0f00373f78be6
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 268 REGISTER

From: ;tag=6ec0e2a2

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bKeb0b5b4594599cf890542f44f9edcfa7
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 191 REGISTER

From: ;tag=46dff306

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK47a29875db648001a4a035421b4aa833
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 517 REGISTER

From: ;tag=b8949006

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK68b52537281b1a802f4d891fdfd0ff9f
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 267 REGISTER

From: ;tag=ff27b51e

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK3dc95c5840f99b7a06c5586cf722b4f0
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 190 REGISTER

From: ;tag=7ca44049

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK1f049117e8706117624c2f75f2a7a12f
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 516 REGISTER

From: ;tag=3a303ce7

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK05943f6285c08324c70ede824887a7a7
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 266 REGISTER

From: ;tag=ad7caa63

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK046817c1aa1816f73b2499e4f635c2c2
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 189 REGISTER

From: ;tag=7ac3508

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK5bf97db9322f292bc1ff08cf6a1d1e28
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 515 REGISTER

From: ;tag=4f0eea87

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bKb817af644db3bfc1221b38a92f8da5dd
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 265 REGISTER

From: ;tag=d04ac708

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK8d01273c22f078b4fab2231eeab5ae9b
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 188 REGISTER

From: ;tag=fcd7b533

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK37718946d666ab6b1719281bb233ab19
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ed443709fa6dfa29aca36cb55584d7f62b687",uri="sip:my.public.WAN.IP",response="ba33f141655d85f4db2f502263879fdb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

MESSAGE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 76023e04ef67cfd271c27dc1100adf72@0.0.0.0
CSeq: 1214005 MESSAGE

From: ;tag=4d20dd4b

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6d30ed01bdbc57e9bc1dc544a6b0c5f1
Max-Forwards: 70
Content-Type: application/im-iscomposing+xml
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Content-Length: 200

idle

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 514 REGISTER

From: ;tag=14de2648

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK983fab6bb0692a4711685df27f6cb7ac
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ed450149bb4114b1029e0d75d6a8d1d96ae33",uri="sip:my.public.WAN.IP",response="f1441a9dcdbaba93a43088f39896a573"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 264 REGISTER

From: ;tag=7ff808ac

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bKbc8fecdc96d6aac46309d36ab6dcb06d
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ed468642d053f8ff03ce5efd4d158463b3db3",uri="sip:my.public.WAN.IP",response="0b94f8f249c117aa20b4454b73bfd6ee"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK55a001e3bf1b2f0a8d24e470399a26a0
Max-Forwards: 70
Contact: "Claudia"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Event: presence
Accept: application/pidf+xml
Expires: 36
Content-Length: 0

SUBSCRIBE sip:Smith1@my.public.WAN.IP SIP/2.0
Call-ID: 8db1ab01c14894034ddc10053891b824@0.0.0.0
CSeq: 1 SUBSCRIBE

From: ;tag=cbe89a12

Regards, Earl

Earl wrote:

···

TO: fields seem strange ???

We are both using build 2366.

Earl wrote:

One more comment. When I click on the down arrow at the top
of the main SC window, I see a green SIP on icon.
But in a SIP chat window the Send Via says SIP off gray.
The SIP server confirms both users registered.

Also the account window has me logged in with green SIP
ON icon. >> >> Earl >> >> Earl wrote:

I see Mr. Smith logged into my server, which is on the same LAN as
myself (MilkFish server openSER embedded). I am also registered.
SIP server is in a LinkSys router, reflashed to DD-WRT v.2.4SP1
O/S.

I added Mr. Smith as a contact, but do not see him green. When I
tried to send him a SIP msg, I got an error report. Interesting that
my Send Via icon says SIP off, even though I see that I am registered
in the server.

Will try from other LAN stations and see if there is a difference.
Will look at the server SIP trace, and later will install pcap and
wireshark.

Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

I changed my numeric public IP to a phrase
Earl and Claudia-4 have both green SIP presence
Earl and Claudia have both gray SIP presence (incorrect)
Mr. Smith (Inet) has gray SIP presence on all LAN computers. (incorrect)
I see no NOTIFY stanzas, which is strange since there are
some SIP green presences.
Will soon install pcap and wireshark to be sure.

The green SIP presence of Claudia-4 is not from a roster
contact that I manually created. It was auto-generated by
SC and put in the group "not in contact list". I did not
do this, although I may have clicked on a pop-up window
auto-generated by SC, asking to accept or reject Claudia-4.
The roster SIP contact that I manually generated for
Claudia-4 showed gray non presence (incorrect) until I
deleted it.

Now that Claudia-4 has become green, the SIP message
window shows green Send Via icon. The computer with
Claudia is still gray.

All the gray SIP presences are from roster contacts that I
manually entered using menus. The only green SIP presence
is with a roster contact that was auto-generated by SC
somehow for some reason.

Earl

SIP Trace
Close and open this window again to update trace...

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 652 REGISTER

From: ;tag=bedd044f

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK766f8389f95773dc113a0b993acce7d4
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 402 REGISTER

From: ;tag=33420541

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK5fc02668565763821ca6883695706333
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 114 REGISTER

From: "Smith1" ;tag=3bbe2bd5

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKbb3d0e16eb159d8463af02470208ed6c
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 113 REGISTER

From: "Smith1" ;tag=9b281377

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKdee9af94f6ba902d6aa1894d5fc63b88
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 325 REGISTER

From: ;tag=5b751e66

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK97f650bd992ddb4d1aa8d0fd849ac4e9
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 651 REGISTER

From: ;tag=d5ed1f7c

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK0e43ce1b91d101f9901c04209fdffa67
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 401 REGISTER

From: ;tag=166bd47e

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK5af49d66887a6152f1e92a19edc1db0a
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 112 REGISTER

From: "Smith1" ;tag=978db196

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKc88acb4022e224e95df47ea34b5b6538
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 111 REGISTER

From: "Smith1" ;tag=7e8d1ac8

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK819f0f13cbf8aea7ca55f59b6f39c32f
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 324 REGISTER

From: ;tag=9076f9f

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bKbd597d48034fa58843f08df0cfb3752d
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 650 REGISTER

From: ;tag=25bd600f

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK7b78bd37be65cf3373ee14b6cd8c406b
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 400 REGISTER

From: ;tag=608bd3f3

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bKea8b04305bacc78d5252f27f008f8ca8
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 110 REGISTER

From: "Smith1" ;tag=5b69cef9

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK1dc3fbecc8e1180715ea48db3fe5e413
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 109 REGISTER

From: "Smith1" ;tag=67ae30d4

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK4eaf2d3e98b8004a2b5df536bd660679
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 323 REGISTER

From: ;tag=bfeded2a

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK6910b6824279f0699bd6357f0ff6900c
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 649 REGISTER

From: ;tag=8a434c83

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK3fea012b7386988f63605f207ca63863
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 399 REGISTER

From: ;tag=b3715642

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK6c28684a0ad742595faad244b05f0470
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 108 REGISTER

From: "Smith1" ;tag=70fb82fb

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK78b8aa28caebb172f1aae2a43766a4ab
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 107 REGISTER

From: "Smith1" ;tag=33439a4c

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKb98a4ffb58b05c8ba974f15560189775
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 322 REGISTER

From: ;tag=6250daa2

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bKb1eed6343be0a009d2f4702be979cbe6
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 648 REGISTER

From: ;tag=61f1f62d

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bKca59eddcdebbcae53aaf7e7a45832bfa
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 398 REGISTER

From: ;tag=8b3fc6b1

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK843e7bbffc07f29586bc4d7563785541
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 106 REGISTER

From: "Smith1" ;tag=b7240ddc

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK88ebe9094c9ea71ac30f5130c25c81bf
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 105 REGISTER

From: "Smith1" ;tag=d4f7741e

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKe289eece25bb9a066706fc42b8a0b32b
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 321 REGISTER

From: ;tag=1e5a75ce

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK1437a6002dfe6cdb6ea1988fa73d9253
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 647 REGISTER

From: ;tag=aa7ae792

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bKe597ab1020fc16278bf24ee97d887a96
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 397 REGISTER

From: ;tag=f78f1ef4

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK33a3829ed37584c84f1526a82f59b66b
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 104 REGISTER

From: "Smith1" ;tag=7d608168

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK94c8d581e8773e4a6c0111340efc1099
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 104 REGISTER

From: "Smith1" ;tag=9ef85b70

Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKc3a442b9455ef90bd2bd0776a013156d
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5ee0b9b2bd4306de95f54e65093a275229a601",uri="sip:my.public.WAN.IP",response="5e59b49d88b0b989aecc29258b73cfcb"
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 103 REGISTER

From: "Smith1" ;tag=9ef85b70

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK8cc9dce5a415d0f0bdbcc0eb7867f983
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5edf8ab68d24c4938f9fbc22d92f5fe9b482d9",uri="sip:my.public.WAN.IP",response="773ffe7f5b116e15f852316790f8575d"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 320 REGISTER

From: ;tag=f2559118

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bK7bb779addaa260d771b45665076f7411
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 646 REGISTER

From: ;tag=b54c47af

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bKfbe589d4733b891b4b7a080759f8957b
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Earl" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: a164e36a8b53585dc4d222c0800c5b32@0.0.0.0
CSeq: 396 REGISTER

From: ;tag=ea7cd5da

To:
Via: SIP/2.0/UDP 192.168.6.14:5060;branch=z9hG4bK51a8022f6bb75ae41480c5ad72401299
Max-Forwards: 70
Authorization: Digest username="claudia-4",realm="my.public.WAN.IP",nonce="4b5ee0406d4f47f3ae4b382d14a3e17593ef0143",uri="sip:my.public.WAN.IP",response="2f60e6eee5d61f7b22bf6926afd16638"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "claudia-4" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 102 REGISTER

From: "Smith1" ;tag=180490bc

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bKeba3b2ba17f42e92f76a9b9bf80c98be
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5edf8ab68d24c4938f9fbc22d92f5fe9b482d9",uri="sip:my.public.WAN.IP",response="773ffe7f5b116e15f852316790f8575d"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: c590f9654bdf379b1b1626f5d0620395@0.0.0.0
CSeq: 101 REGISTER

From: "Smith1" ;tag=2475382e

Via: SIP/2.0/UDP 141.14.245.68:5060;branch=z9hG4bK42a176029485a6756a049e57dd09fe06
Max-Forwards: 70
Authorization: Digest username="Smith1",realm="my.public.WAN.IP",nonce="4b5edf8ab68d24c4938f9fbc22d92f5fe9b482d9",uri="sip:my.public.WAN.IP",response="773ffe7f5b116e15f852316790f8575d"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2367Windows XP
Expires: 3600
Contact: "Smith1" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 580ae0372ada47969bfec6a0ce5442c3@0.0.0.0
CSeq: 319 REGISTER

From: ;tag=b621e2f8

To:
Via: SIP/2.0/UDP 192.168.6.13:5060;branch=z9hG4bKba04a22feabc1fa09c74e6f211fd1c5b
Max-Forwards: 70
Authorization: Digest username="Claudia",realm="my.public.WAN.IP",nonce="4b5ee017fa0f5bcec32ea3ae6e1f0aab6d7662e4",uri="sip:my.public.WAN.IP",response="2ea3c5048f3cd6a7e38fa63d411d2515"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600
Contact: "Claudia" ;expires=3600
Content-Length: 0

REGISTER sip:my.public.WAN.IP SIP/2.0
Call-ID: 3f5cf40927be811db43cde813ac6acaa@0.0.0.0
CSeq: 645 REGISTER

From: ;tag=cedbd7ec

To:
Via: SIP/2.0/UDP 192.168.6.146:5060;branch=z9hG4bK89861adf5804d24fb83a8b39264b8153
Max-Forwards: 70
Authorization: Digest username="Earl",realm="my.public.WAN.IP",nonce="4b5ee02764a6c3e432921168d6eea77d49c14c44",uri="sip:my.public.WAN.IP",response="cd0d0e4b7dd58fe5793e783d0a9628ba"
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2366Windows XP
Expires: 3600

···

To: "Smith1"

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

Since it seems important to the SIP presence problem to know
what is the difference between manually generated roster contact
and one auto-generated by SC,
how do I find on a WIN computer and post here the database
info that contains all SIP roster info. Comparing the roster info
for a contact that correctly gives SIP presence with one that
does not work correctly could help to identify the problem.

One computer has two roster contacts for the same person, but
one contact is green and the other is gray. I would like to know
what difference there is between these two contacts as stored
by SC in a file somewhere? How can I obtain this info?

Earl

Earl wrote:

···

[snip]

The green SIP presence of Claudia-4 is not from a roster
contact that I manually created. It was auto-generated by
SC and put in the group "not in contact list". I did not
do this, although I may have clicked on a pop-up window
auto-generated by SC, asking to accept or reject Claudia-4.
The roster SIP contact that I manually generated for
Claudia-4 showed gray non presence (incorrect) until I
deleted it.

[snip]
All the gray SIP presences are from roster contacts that I
manually entered using menus. The only green SIP presence
is with a roster contact that was auto-generated by SC
somehow for some reason.

Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Making progress on the green presence indicator. I had to leave and so I
turned off the computer and upon my return, rebooted.
Sometime later I noticed Mr. Smith was green, so we were able to SIP
chat. He wanted to see what would happen if he turned SC off and on.
I kept the chat window open. The chat window said unknown then offline,
then unknown. Mr Smith never became online. Even though "offline" and
gray, we could continue to chat. Before a chat when "offline" was impossible
and would always generate an error msg. Maybe because I kept the chat
window open?

So I said that I was going to add an entry in the SIP registrar called
smith1 in addition to the original Smith1. As soon as I did this, Smith1
instantly turned from gray to green, while smith1 in roster stayed gray.
The registration trace becomes interesting, now showing 2 Smiths at
different IPs. See attached images. The areas that I grayed out for
confidentiality are the same. Perhaps home and office computers at
different IPs ? However, the other computer would have Smith2 and
not Smith1 as ID, I would think ???

What this means is that I have to do some tests in the registrar and with
clients if there is a "small letters and capital letters" problem. Even if
Windows does not care, Linux does. My server runs on Linux, as many
others do.

Will post more when I have test results.

Earl

Earl wrote:

···

Since it seems important to the SIP presence problem to know
what is the difference between manually generated roster contact
and one auto-generated by SC,
how do I find on a WIN computer and post here the database
info that contains all SIP roster info. Comparing the roster info
for a contact that correctly gives SIP presence with one that
does not work correctly could help to identify the problem.

One computer has two roster contacts for the same person, but
one contact is green and the other is gray. I would like to know
what difference there is between these two contacts as stored
by SC in a file somewhere? How can I obtain this info?

Earl

Earl wrote:

[snip]

The green SIP presence of Claudia-4 is not from a roster
contact that I manually created. It was auto-generated by
SC and put in the group "not in contact list". I did not
do this, although I may have clicked on a pop-up window
auto-generated by SC, asking to accept or reject Claudia-4.
The roster SIP contact that I manually generated for
Claudia-4 showed gray non presence (incorrect) until I
deleted it.

[snip]
All the gray SIP presences are from roster contacts that I
manually entered using menus. The only green SIP presence
is with a roster contact that was auto-generated by SC
somehow for some reason.

Earl


#14

Hi,

I will try to answer most of the observations you have made and tell you
what I've tested :slight_smile:

1. > I added Mr. Smith as a contact, but do not see him green. Interesting
that my Send Via icon says SIP off, even though I see that I am registered
in the server.

This is normal behaviour as the contact you send message is offline "Send
Via" indicates the account you use and the status of the body you are
contacting.

2. I'm not sure about MilkFish does it support presence.

3. I have started again the sip tests, for more than a week they are running
with every build and haven't failed till now.
The server is latest OpenSIPS with presence and nathelper enabled.

For me when "Force P2P presence" is not enabled on all sides and there is
presence support on the server everything works ok.

Cheers
damencho

···

On Tue, Jan 26, 2010 at 8:34 PM, Earl <Large.Files@gmx.net> wrote:

Making progress on the green presence indicator. I had to leave and so I
turned off the computer and upon my return, rebooted.
Sometime later I noticed Mr. Smith was green, so we were able to SIP
chat. He wanted to see what would happen if he turned SC off and on.
I kept the chat window open. The chat window said unknown then offline,
then unknown. Mr Smith never became online. Even though "offline" and
gray, we could continue to chat. Before a chat when "offline" was
impossible
and would always generate an error msg. Maybe because I kept the chat
window open?

So I said that I was going to add an entry in the SIP registrar called
smith1 in addition to the original Smith1. As soon as I did this, Smith1
instantly turned from gray to green, while smith1 in roster stayed gray.
The registration trace becomes interesting, now showing 2 Smiths at
different IPs. See attached images. The areas that I grayed out for
confidentiality are the same. Perhaps home and office computers at
different IPs ? However, the other computer would have Smith2 and
not Smith1 as ID, I would think ???

What this means is that I have to do some tests in the registrar and with
clients if there is a "small letters and capital letters" problem. Even if
Windows does not care, Linux does. My server runs on Linux, as many
others do.

Will post more when I have test results.

Earl

Earl wrote:

Since it seems important to the SIP presence problem to know
what is the difference between manually generated roster contact
and one auto-generated by SC,
how do I find on a WIN computer and post here the database
info that contains all SIP roster info. Comparing the roster info
for a contact that correctly gives SIP presence with one that
does not work correctly could help to identify the problem.

One computer has two roster contacts for the same person, but
one contact is green and the other is gray. I would like to know
what difference there is between these two contacts as stored
by SC in a file somewhere? How can I obtain this info?

Earl

Earl wrote:

[snip]

The green SIP presence of Claudia-4 is not from a roster
contact that I manually created. It was auto-generated by
SC and put in the group "not in contact list". I did not
do this, although I may have clicked on a pop-up window
auto-generated by SC, asking to accept or reject Claudia-4.
The roster SIP contact that I manually generated for
Claudia-4 showed gray non presence (incorrect) until I
deleted it.

[snip]
All the gray SIP presences are from roster contacts that I
manually entered using menus. The only green SIP presence
is with a roster contact that was auto-generated by SC
somehow for some reason.

Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#15

Damian

I have not had time to do any more testing with Mr. Smith, but our last tests
showed:

I turn on my computer and MS is green present. I send him a SIP msg and
he says I am gray. He then reboots SC and he sees me green, but now I
see him gray. This scenario has happened several times using WIN and
several of the latest builds.

Apparently Milkfish (OpenSER v1.0) does support presence since we
do sometimes see green presence.
We both have unchecked "Force P2P presence".

Does NAThelper in OpenSIPS really help to traverse the NAT?
Is this internal to OpenSIPS or is this a Linux kernel module that is
loaded and independent of OpenSIPS ?

I have the option to eventually use OpenSER, Kamailio, or OpenSIPS
- or even SIPwitch. What are your opinions ?

Earl

Damian Minkov wrote:

···

Hi,

I will try to answer most of the observations you have made and tell you what I've tested :slight_smile:

1. > I added Mr. Smith as a contact, but do not see him green. Interesting that my Send Via icon says SIP off, even though I see that I am registered in the server.

This is normal behaviour as the contact you send message is offline "Send Via" indicates the account you use and the status of the body you are contacting.

2. I'm not sure about MilkFish does it support presence.

3. I have started again the sip tests, for more than a week they are running with every build and haven't failed till now.
The server is latest OpenSIPS with presence and nathelper enabled.

For me when "Force P2P presence" is not enabled on all sides and there is presence support on the server everything works ok.

Cheers
damencho

On Tue, Jan 26, 2010 at 8:34 PM, Earl <Large.Files@gmx.net > <mailto:Large.Files@gmx.net>> wrote:

    Making progress on the green presence indicator. I had to leave
    and so I
    turned off the computer and upon my return, rebooted.
    Sometime later I noticed Mr. Smith was green, so we were able to SIP
    chat. He wanted to see what would happen if he turned SC off and on.
    I kept the chat window open. The chat window said unknown then
    offline,
    then unknown. Mr Smith never became online. Even though
    "offline" and
    gray, we could continue to chat. Before a chat when "offline" was
    impossible
    and would always generate an error msg. Maybe because I kept the chat
    window open?

    So I said that I was going to add an entry in the SIP registrar called
    smith1 in addition to the original Smith1. As soon as I did this,
    Smith1
    instantly turned from gray to green, while smith1 in roster stayed
    gray.
    The registration trace becomes interesting, now showing 2 Smiths at
    different IPs. See attached images. The areas that I grayed out for
    confidentiality are the same. Perhaps home and office computers at
    different IPs ? However, the other computer would have Smith2 and
    not Smith1 as ID, I would think ???

    What this means is that I have to do some tests in the registrar
    and with
    clients if there is a "small letters and capital letters" problem.
     Even if
    Windows does not care, Linux does. My server runs on Linux, as many
    others do.

    Will post more when I have test results.

    Earl

    Earl wrote:

        Since it seems important to the SIP presence problem to know
        what is the difference between manually generated roster contact
        and one auto-generated by SC,
        how do I find on a WIN computer and post here the database
        info that contains all SIP roster info. Comparing the roster info
        for a contact that correctly gives SIP presence with one that
        does not work correctly could help to identify the problem.

        One computer has two roster contacts for the same person, but
        one contact is green and the other is gray. I would like to know
        what difference there is between these two contacts as stored
        by SC in a file somewhere? How can I obtain this info?

        Earl

        Earl wrote:

            [snip]

            The green SIP presence of Claudia-4 is not from a roster
            contact that I manually created. It was auto-generated by
            SC and put in the group "not in contact list". I did not
            do this, although I may have clicked on a pop-up window
            auto-generated by SC, asking to accept or reject Claudia-4.
            The roster SIP contact that I manually generated for
            Claudia-4 showed gray non presence (incorrect) until I
            deleted it.

            [snip]
            All the gray SIP presences are from roster contacts that I
            manually entered using menus. The only green SIP presence
            is with a roster contact that was auto-generated by SC
            somehow for some reason.

            Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Hi,

nathelper is opensips module which can handle sdp and sip in order devices
to work when they are behind nat, other sip servers also has such modules.
So if you have not enabled such a module and your clients are behind NAT it
can be that the unexpected behaviour comes from that.

Cheers
damencho

···

On Thu, Feb 11, 2010 at 10:37 AM, Earl <Large.Files@gmx.net> wrote:

Damian

I have not had time to do any more testing with Mr. Smith, but our last
tests
showed:

I turn on my computer and MS is green present. I send him a SIP msg and
he says I am gray. He then reboots SC and he sees me green, but now I
see him gray. This scenario has happened several times using WIN and
several of the latest builds.

Apparently Milkfish (OpenSER v1.0) does support presence since we
do sometimes see green presence.
We both have unchecked "Force P2P presence".

Does NAThelper in OpenSIPS really help to traverse the NAT?
Is this internal to OpenSIPS or is this a Linux kernel module that is
loaded and independent of OpenSIPS ?

I have the option to eventually use OpenSER, Kamailio, or OpenSIPS
- or even SIPwitch. What are your opinions ?

Earl

Damian Minkov wrote:

Hi,

I will try to answer most of the observations you have made and tell you
what I've tested :slight_smile:

1. > I added Mr. Smith as a contact, but do not see him green. Interesting
that my Send Via icon says SIP off, even though I see that I am registered
in the server.

This is normal behaviour as the contact you send message is offline "Send
Via" indicates the account you use and the status of the body you are
contacting.

2. I'm not sure about MilkFish does it support presence.

3. I have started again the sip tests, for more than a week they are
running with every build and haven't failed till now.
The server is latest OpenSIPS with presence and nathelper enabled.

For me when "Force P2P presence" is not enabled on all sides and there is
presence support on the server everything works ok.

Cheers
damencho

On Tue, Jan 26, 2010 at 8:34 PM, Earl <Large.Files@gmx.net <mailto: >> Large.Files@gmx.net>> wrote:

   Making progress on the green presence indicator. I had to leave
   and so I
   turned off the computer and upon my return, rebooted.
   Sometime later I noticed Mr. Smith was green, so we were able to SIP
   chat. He wanted to see what would happen if he turned SC off and on.
   I kept the chat window open. The chat window said unknown then
   offline,
   then unknown. Mr Smith never became online. Even though
   "offline" and
   gray, we could continue to chat. Before a chat when "offline" was
   impossible
   and would always generate an error msg. Maybe because I kept the chat
   window open?

   So I said that I was going to add an entry in the SIP registrar called
   smith1 in addition to the original Smith1. As soon as I did this,
   Smith1
   instantly turned from gray to green, while smith1 in roster stayed
   gray.
   The registration trace becomes interesting, now showing 2 Smiths at
   different IPs. See attached images. The areas that I grayed out for
   confidentiality are the same. Perhaps home and office computers at
   different IPs ? However, the other computer would have Smith2 and
   not Smith1 as ID, I would think ???

   What this means is that I have to do some tests in the registrar
   and with
   clients if there is a "small letters and capital letters" problem.
    Even if
   Windows does not care, Linux does. My server runs on Linux, as many
   others do.

   Will post more when I have test results.

   Earl

   Earl wrote:

       Since it seems important to the SIP presence problem to know
       what is the difference between manually generated roster contact
       and one auto-generated by SC,
       how do I find on a WIN computer and post here the database
       info that contains all SIP roster info. Comparing the roster info
       for a contact that correctly gives SIP presence with one that
       does not work correctly could help to identify the problem.

       One computer has two roster contacts for the same person, but
       one contact is green and the other is gray. I would like to know
       what difference there is between these two contacts as stored
       by SC in a file somewhere? How can I obtain this info?

       Earl

       Earl wrote:

           [snip]

           The green SIP presence of Claudia-4 is not from a roster
           contact that I manually created. It was auto-generated by
           SC and put in the group "not in contact list". I did not
           do this, although I may have clicked on a pop-up window
           auto-generated by SC, asking to accept or reject Claudia-4.
           The roster SIP contact that I manually generated for
           Claudia-4 showed gray non presence (incorrect) until I
           deleted it.

           [snip]
           All the gray SIP presences are from roster contacts that I
           manually entered using menus. The only green SIP presence
           is with a roster contact that was auto-generated by SC
           somehow for some reason.

           Earl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net