< Previous by Date	Date Index	Next by Date >
	Thread Index	Next in Thread >

[reSIProcate-users] How can sip stack stop when same user login another PC?

From: 이영한 <websearch@xxxxxxxxx>
Date: Mon, 11 Aug 2008 16:21:16 +0900

I'm a SIP server programmer. My SIP server has presence.winfo function. I test with X-Lite which use reSIProcate sip stack.

I would like to stop sip stack or logout when same user login at another PC. My scenario is like below.

1. user A login at PC A.

2. user A send presence.winfo SUBSCRIBE to SIP server

3. user A login at PC B.

4. SIP server send NOTIFY to PC A.

- but sip stack is not stopped at PC A.

- How can make sip stack stop or logout?

My SIP server log of upper scenario is like below.

[16:11:55.062000] [NETWORK] [2464] recv from(127.0.0.1:17060,3840) [REGISTER sip:127.0.0.1:5090 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-c92b027ff141ff58-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:1234@xxxxxxxxx:17060;rinstance=42215a160ed658d5>

To: "1234"<sip:1234@xxxxxxxxx:5090>

From: "1234"<sip:1234@xxxxxxxxx:5090>;tag=51272635

Call-ID: MjFhMzUxMjIzZjE5YjY4ODQ3MDg0MGMxNWE4NTUzNjM.

CSeq: 1 REGISTER

Expires: 3600

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

User-Agent: X-Lite release 1100l stamp 47546

Content-Length: 0

]

[16:11:55.156000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-c92b027ff141ff58-1---d8754z-;rport=17060

From: "1234" <sip:1234@xxxxxxxxx:5090>;tag=51272635

To: "1234" <sip:1234@xxxxxxxxx:5090>;tag=2256673146

Call-ID: MjFhMzUxMjIzZjE5YjY4ODQ3MDg0MGMxNWE4NTUzNjM.

CSeq: 1 REGISTER

WWW-Authenticate: Digest realm="testsip.com", nonce="63d87ff12fec104fefaf961c85487943"

Content-Length: 0

]

[16:11:55.359000] [NETWORK] [2464] recv from(127.0.0.1:17060,3840) [REGISTER sip:127.0.0.1:5090 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-01405619700ef40b-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:1234@xxxxxxxxx:17060;rinstance=42215a160ed658d5>

To: "1234"<sip:1234@xxxxxxxxx:5090>

From: "1234"<sip:1234@xxxxxxxxx:5090>;tag=51272635

Call-ID: MjFhMzUxMjIzZjE5YjY4ODQ3MDg0MGMxNWE4NTUzNjM.

CSeq: 2 REGISTER

Expires: 3600

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

User-Agent: X-Lite release 1100l stamp 47546

Authorization: Digest username="1234",realm="testsip.com",nonce="63d87ff12fec104fefaf961c85487943",uri="sip:127.0.0.1:5090",response="e3bd79f99549143974117d27362a5f45",algorithm=MD5

Content-Length: 0

]

[16:11:55.531000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [SIP/2.0 100 Trying

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-01405619700ef40b-1---d8754z-;rport=17060

From: "1234" <sip:1234@xxxxxxxxx:5090>;tag=51272635

To: "1234" <sip:1234@xxxxxxxxx:5090>

Call-ID: MjFhMzUxMjIzZjE5YjY4ODQ3MDg0MGMxNWE4NTUzNjM.

CSeq: 2 REGISTER

Content-Length: 0

]

[16:11:55.687000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-01405619700ef40b-1---d8754z-;rport=17060

From: "1234" <sip:1234@xxxxxxxxx:5090>;tag=51272635

To: "1234" <sip:1234@xxxxxxxxx:5090>;tag=827869967

Call-ID: MjFhMzUxMjIzZjE5YjY4ODQ3MDg0MGMxNWE4NTUzNjM.

CSeq: 2 REGISTER

Contact: <sip:1234@xxxxxxxxx:17060;rinstance=42215a160ed658d5>;EXPIRES=1800

Content-Length: 0

]

[16:11:55.796000] [NETWORK] [2464] recv from(127.0.0.1:17060,3840) [SUBSCRIBE sip:1234@xxxxxx SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-06400821165a4f65-1---d8754z-;rport

Max-Forwards: 70

Contact: <sip:1234@xxxxxxxxx:17060>

To: <sip:1234@xxxxxx>

From: "1234"<sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 1 SUBSCRIBE

Expires: 3600

Accept: application/watcherinfo+xml

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

User-Agent: X-Lite release 1100l stamp 47546

Event: presence.winfo

Content-Length: 0

]

[16:11:55.953000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:17060;branch=z9hG4bK-d8754z-06400821165a4f65-1---d8754z-;rport=17060

From: "1234" <sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

To: <sip:1234@xxxxxx>;tag=1887025096

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 1 SUBSCRIBE

Contact: <sip:127.0.0.1:5090>

Content-Length: 0

]

[16:11:56.140000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [NOTIFY sip:1234@xxxxxxxxx:17060 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bKl-683a510d105ce41082aa9747c4a803ee;rport

Route: <sip:127.0.0.1:17060;lr>

From: <sip:1234@xxxxxxxxx:5090>;tag=1887025096

To: <sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 2 NOTIFY

Contact: <sip:127.0.0.1:5090>

Max-Forwards: 70

Subscription-State: active

Event: presence.winfo

Content-Length: 286

<?xml version="1.0"?>
<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="0" state="full">
<watcher-list resource="sip:1234@xxxxxxxxx:5090" package="presence">
<watcher id="1" event="approved" status="active">sip:1234@xxxxxxxxx:5090</watcher>
</watcher-list>
</watcherinfo>]

[16:11:56.250000] [NETWORK] [2464] recv from(127.0.0.1:17060,3840) [SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bKl-683a510d105ce41082aa9747c4a803ee;rport=5090

Contact: <sip:1234@xxxxxxxxx:17060>

To: <sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

From: <sip:1234@xxxxxxxxx:5090>;tag=1887025096

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 2 NOTIFY

User-Agent: X-Lite release 1100l stamp 47546

Content-Length: 0

]

# new client is logined

[16:12:14.390000] [NETWORK] [2464] recv from(127.0.0.1:5061,3840) [REGISTER sip:127.0.0.1 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5061;branch=3240294560;rport=

From: <sip:1234@xxxxxxxxx>;tag=3836

To: <sip:1234@xxxxxxxxx>;tag=3836

Call-ID: 2663354558@xxxxxxxxx

CSeq: 8 REGISTER

Contact: <sip:1234@xxxxxxxxx:5061>

Expires: 300

Max-Forwards: 70

User-Agent: SipClient

Content-Length: 0

]

[16:12:14.437000] [NETWORK] [3156] send to(127.0.0.1:5061,3840) [SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 127.0.0.1:5061;branch=3240294560;rport=5061

From: <sip:1234@xxxxxxxxx>;tag=3836

To: <sip:1234@xxxxxxxxx>;tag=3836

Call-ID: 2663354558@xxxxxxxxx

CSeq: 8 REGISTER

WWW-Authenticate: Digest realm="testsip.com", nonce="945e07edb0acf8e18c9fc65bff6927db"

Content-Length: 0

]

[16:12:14.437000] [NETWORK] [2464] recv from(127.0.0.1:5061,3840) [REGISTER sip:127.0.0.1 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5061;branch=1576260065;rport=

From: <sip:1234@xxxxxxxxx>;tag=3836

To: <sip:1234@xxxxxxxxx>;tag=3836

Call-ID: 2663354558@xxxxxxxxx

CSeq: 9 REGISTER

Contact: <sip:1234@xxxxxxxxx:5061>

Authorization: Digest username="1234", realm="testsip.com", nonce="945e07edb0acf8e18c9fc65bff6927db", uri="sip:127.0.0.1", response="37fa86b20444f5191f75333ce232231b"

Expires: 300

Max-Forwards: 70

User-Agent: SipClient

Content-Length: 0

]

[16:12:14.453000] [NETWORK] [3156] send to(127.0.0.1:5061,3840) [SIP/2.0 100 Trying

Via: SIP/2.0/UDP 127.0.0.1:5061;branch=1576260065;rport=5061

From: <sip:1234@xxxxxxxxx>;tag=3836

To: <sip:1234@xxxxxxxxx>;tag=3836

Call-ID: 2663354558@xxxxxxxxx

CSeq: 9 REGISTER

Content-Length: 0

]

[16:12:14.593000] [NETWORK] [3156] send to(127.0.0.1:5061,3840) [SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:5061;branch=1576260065;rport=5061

From: <sip:1234@xxxxxxxxx>;tag=3836

To: <sip:1234@xxxxxxxxx>;tag=3836

Call-ID: 2663354558@xxxxxxxxx

CSeq: 9 REGISTER

Contact: <sip:1234@xxxxxxxxx:5061>;EXPIRES=300

Content-Length: 0

]

[16:12:14.656000] [NETWORK] [3156] send to(127.0.0.1:17060,3840) [NOTIFY sip:1234@xxxxxxxxx:17060 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bKl-0be090f04c3204fd1914c72072fa61ff;rport

Route: <sip:127.0.0.1:17060;lr>

From: <sip:1234@xxxxxxxxx:5090>;tag=1887025096

To: <sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 3 NOTIFY

Contact: <sip:127.0.0.1:5090>

Max-Forwards: 70

Subscription-State: terminated

Event: presence.winfo

Content-Length: 290

<?xml version="1.0"?>
<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="0" state="full">
<watcher-list resource="sip:1234@xxxxxxxxx:5090" package="presence">
<watcher id="1" event="rejected" status="terminated">sip:1234@xxxxxxxxx:5090</watcher>
</watcher-list>
</watcherinfo>]

[16:12:14.750000] [NETWORK] [2464] recv from(127.0.0.1:17060,3840) [SIP/2.0 200 OK

Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bKl-0be090f04c3204fd1914c72072fa61ff;rport=5090

Contact: <sip:1234@xxxxxxxxx:17060>

To: <sip:1234@xxxxxxxxx:5090>;tag=d5327d2a

From: <sip:1234@xxxxxxxxx:5090>;tag=1887025096

Call-ID: ZDk2MzY4ODJlYzRiZDc4MjIzMTA3M2E5YTI4MzY3ZjY.

CSeq: 3 NOTIFY

User-Agent: X-Lite release 1100l stamp 47546

Content-Length: 0

]

Follow-Ups:
- Re: [reSIProcate-users] How can sip stack stop when same user login another PC?
  - From: Scott Godin

Prev by Date: Re: [reSIProcate-users] usage of TLS
Next by Date: [reSIProcate-users] ending a dialog / session and free all the resources.
Previous by thread: Re: [reSIProcate-users] usage of TLS
Next by thread: Re: [reSIProcate-users] How can sip stack stop when same user login another PC?
Index(es):
- Date
- Thread