Jump to content

Restart service to register


Ganesh

Recommended Posts

Sometimes the registration of phones goes off. If the pbxnsip service is restarted, the phones then gets registered. Below is the logs taken before the service was restarted.

 

[7] 2008/07/14 12:06:09:

SIP Rx udp:10.255.109.71:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.109.71:5060;branch=z9hG4bK8277290331884624686;rport

From: 9 <sip:9@10.255.10.41:5060>;tag=72856

To: 9 <sip:9@10.255.10.41:5060>

Call-ID: 156118939-2437221063@10.255.109.71

CSeq: 79 REGISTER

Contact: <sip:9@10.255.109.71:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:09:

Resolve 1427946: aaaa udp 10.255.109.71 5060

 

[9] 2008/07/14 12:06:09:

Resolve 1427946: a udp 10.255.109.71 5060

 

[9] 2008/07/14 12:06:09:

Resolve 1427946: udp 10.255.109.71 5060

 

[7] 2008/07/14 12:06:09:

SIP Tx udp:10.255.109.71:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.109.71:5060;branch=z9hG4bK8277290331884624686;rport=5060

From: 9 <sip:9@10.255.10.41:5060>;tag=72856

To: 9 <sip:9@10.255.10.41:5060>;tag=01b3b5008d

Call-ID: 156118939-2437221063@10.255.109.71

CSeq: 79 REGISTER

Contact: <sip:9@10.255.109.71:5060>;expires=28

Content-Length: 0

 

[7] 2008/07/14 12:06:10:

SIP Rx udp:10.255.109.224:5060:

 

REGISTER sip:10.255.10.41 SIP/2.0

Via: SIP/2.0/UDP 10.255.109.224:5060;branch=z9hG4bK-6rcuu3t7ad56;rport

From: <sip:43@10.255.10.41>;tag=y2otc1x8wx

To: <sip:43@10.255.10.41>

Call-ID: 3c2670094baf-p6vrwsbpjxvf@10-255-109-224

CSeq: 155034 REGISTER

Max-Forwards: 70

Contact: <sip:43@10.255.109.224:5060;line=o9r6pvlu>;q=1.0

User-Agent: snom190-3.56y

P-NAT-Refresh: 15

Supported: gruu

Allow-Events: dialog

X-Real-IP: 10.255.109.224

WWW-Contact: <http://10.255.109.224:80>

WWW-Contact: <https://10.255.109.224:443>

Expires: 3600

Content-Length: 0

 

[9] 2008/07/14 12:06:10:

Resolve 1427947: aaaa udp 10.255.109.224 5060

 

[9] 2008/07/14 12:06:10:

Resolve 1427947: a udp 10.255.109.224 5060

 

[9] 2008/07/14 12:06:10:

Resolve 1427947: udp 10.255.109.224 5060

 

[7] 2008/07/14 12:06:10:

SIP Tx udp:10.255.109.224:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.109.224:5060;branch=z9hG4bK-6rcuu3t7ad56;rport=5060

From: <sip:43@10.255.10.41>;tag=y2otc1x8wx

To: <sip:43@10.255.10.41>;tag=090a661bac

Call-ID: 3c2670094baf-p6vrwsbpjxvf@10-255-109-224

CSeq: 155034 REGISTER

Contact: <sip:43@10.255.109.224:5060;line=o9r6pvlu>;expires=32

Content-Length: 0

 

[7] 2008/07/14 12:06:12:

SIP Rx udp:10.255.109.195:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.109.195:5060;branch=z9hG4bK1116514926326271659;rport

From: 2204 <sip:2204@10.255.10.41:5060>;tag=69916352

To: 2204 <sip:2204@10.255.10.41:5060>

Call-ID: 35631225-1727829012@10.255.109.195

CSeq: 80 REGISTER

Contact: <sip:2204@10.255.109.195:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:12:

Resolve 1427948: aaaa udp 10.255.109.195 5060

 

[9] 2008/07/14 12:06:12:

Resolve 1427948: a udp 10.255.109.195 5060

 

[9] 2008/07/14 12:06:12:

Resolve 1427948: udp 10.255.109.195 5060

 

[7] 2008/07/14 12:06:12:

SIP Tx udp:10.255.109.195:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.109.195:5060;branch=z9hG4bK1116514926326271659;rport=5060

From: 2204 <sip:2204@10.255.10.41:5060>;tag=69916352

To: 2204 <sip:2204@10.255.10.41:5060>;tag=ee3bc096d6

Call-ID: 35631225-1727829012@10.255.109.195

CSeq: 80 REGISTER

Contact: <sip:2204@10.255.109.195:5060>;expires=32

Content-Length: 0

 

[7] 2008/07/14 12:06:13:

SIP Rx udp:10.255.104.164:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.104.164:5060;branch=z9hG4bK2418523389318324723;rport

From: 4236 <sip:4236@10.255.10.41:5060>;tag=135019576

To: 4236 <sip:4236@10.255.10.41:5060>

Call-ID: 451013859-679113950@10.255.104.164

CSeq: 80 REGISTER

Contact: <sip:4236@10.255.104.164:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:13:

Resolve 1427949: aaaa udp 10.255.104.164 5060

 

[9] 2008/07/14 12:06:13:

Resolve 1427949: a udp 10.255.104.164 5060

 

[9] 2008/07/14 12:06:13:

Resolve 1427949: udp 10.255.104.164 5060

 

[7] 2008/07/14 12:06:13:

SIP Tx udp:10.255.104.164:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.104.164:5060;branch=z9hG4bK2418523389318324723;rport=5060

From: 4236 <sip:4236@10.255.10.41:5060>;tag=135019576

To: 4236 <sip:4236@10.255.10.41:5060>;tag=dd7e486634

Call-ID: 451013859-679113950@10.255.104.164

CSeq: 80 REGISTER

Contact: <sip:4236@10.255.104.164:5060>;expires=31

Content-Length: 0

 

[7] 2008/07/14 12:06:16:

SIP Rx udp:10.255.104.111:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.104.111:5060;branch=z9hG4bK11025564791679386;rport

From: 3166 <sip:3166@10.255.10.41:5060>;tag=135019576

To: 3166 <sip:3166@10.255.10.41:5060>

Call-ID: 2046212465-2842810015@10.255.104.111

CSeq: 79 REGISTER

Contact: <sip:3166@10.255.104.111:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:16:

Resolve 1427950: aaaa udp 10.255.104.111 5060

 

[9] 2008/07/14 12:06:16:

Resolve 1427950: a udp 10.255.104.111 5060

 

[9] 2008/07/14 12:06:16:

Resolve 1427950: udp 10.255.104.111 5060

 

[7] 2008/07/14 12:06:16:

SIP Tx udp:10.255.104.111:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.104.111:5060;branch=z9hG4bK11025564791679386;rport=5060

From: 3166 <sip:3166@10.255.10.41:5060>;tag=135019576

To: 3166 <sip:3166@10.255.10.41:5060>;tag=a9e73364a9

Call-ID: 2046212465-2842810015@10.255.104.111

CSeq: 79 REGISTER

Contact: <sip:3166@10.255.104.111:5060>;expires=29

Content-Length: 0

 

[7] 2008/07/14 12:06:17:

SIP Rx udp:10.255.115.95:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.115.95:5060;branch=z9hG4bK1955631062293118923;rport

From: 2156 <sip:2156@10.255.10.41:5060>;tag=750122006

To: 2156 <sip:2156@10.255.10.41:5060>

Call-ID: 222317741-141084356@10.255.115.95

CSeq: 79 REGISTER

Contact: <sip:2156@10.255.115.95:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:17:

Resolve 1427951: aaaa udp 10.255.115.95 5060

 

[9] 2008/07/14 12:06:17:

Resolve 1427951: a udp 10.255.115.95 5060

 

[9] 2008/07/14 12:06:17:

Resolve 1427951: udp 10.255.115.95 5060

 

[7] 2008/07/14 12:06:17:

SIP Tx udp:10.255.115.95:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.115.95:5060;branch=z9hG4bK1955631062293118923;rport=5060

From: 2156 <sip:2156@10.255.10.41:5060>;tag=750122006

To: 2156 <sip:2156@10.255.10.41:5060>;tag=c43cb57955

Call-ID: 222317741-141084356@10.255.115.95

CSeq: 79 REGISTER

Contact: <sip:2156@10.255.115.95:5060>;expires=30

Content-Length: 0

 

[7] 2008/07/14 12:06:17:

SIP Rx udp:10.255.109.70:5060:

 

REGISTER sip:10.255.10.41:5060 SIP/2.0

Via: SIP/2.0/UDP 10.255.109.70:5060;branch=z9hG4bK25280275672505723734;rport

From: 1233 <sip:1233@10.255.10.41:5060>;tag=496127447

To: 1233 <sip:1233@10.255.10.41:5060>

Call-ID: 261183116-1195921186@10.255.109.70

CSeq: 79 REGISTER

Contact: <sip:1233@10.255.109.70:5060>

Max-Forwards: 70

Expires: 60

User-Agent: Voip Phone 1.0

Content-Length: 0

 

[9] 2008/07/14 12:06:17:

Resolve 1427952: aaaa udp 10.255.109.70 5060

 

[9] 2008/07/14 12:06:17:

Resolve 1427952: a udp 10.255.109.70 5060

 

[9] 2008/07/14 12:06:17:

Resolve 1427952: udp 10.255.109.70 5060

 

[7] 2008/07/14 12:06:17:

SIP Tx udp:10.255.109.70:5060:

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 10.255.109.70:5060;branch=z9hG4bK25280275672505723734;rport=5060

From: 1233 <sip:1233@10.255.10.41:5060>;tag=496127447

To: 1233 <sip:1233@10.255.10.41:5060>;tag=4d22fcf143

Call-ID: 261183116-1195921186@10.255.109.70

CSeq: 79 REGISTER

Contact: <sip:1233@10.255.109.70:5060>;expires=31

Content-Length: 0

 

[4] 2008/07/14 12:06:19:

select returns error

 

[4] 2008/07/14 12:11:39:

Last message repeated 97657610 times

 

[5] 2008/07/14 12:11:39:

RTP Timeout on 28338137515610-209372138317486@10.255.104.164#307532807f

 

[9] 2008/07/14 12:11:39:

Resolve 1427953: url sip:4236@10.255.104.164:5060

 

[9] 2008/07/14 12:11:39:

Resolve 1427953: udp 10.255.104.164 5060

 

[7] 2008/07/14 12:11:39:

03712b05@pbx#504965278: Media-aware pass-through mode

 

[4] 2008/07/14 12:11:39:

select returns error

 

[4] 2008/07/14 12:11:39:

Last message repeated 19 times

 

[9] 2008/07/14 12:11:39:

Resolve 1427954: url sip:202.71.134.13:5060

 

[9] 2008/07/14 12:11:39:

Resolve 1427954: udp 202.71.134.13 5060

 

[4] 2008/07/14 12:11:39:

select returns error

 

[4] 2008/07/14 12:11:47:

Last message repeated 2309856 times

 

[5] 2008/07/14 12:11:47:

Call 03712b05@pbx#504965278: Last request not finished

 

[9] 2008/07/14 12:11:47:

Resolve 1427955: url sip:202.71.134.13:5060

 

[9] 2008/07/14 12:11:47:

Resolve 1427955: udp 202.71.134.13 5060

 

[8] 2008/07/14 12:11:47:

Hangup: Call 03712b05@pbx#504965278 not found

 

[4] 2008/07/14 12:11:47:

select returns error

Link to comment
Share on other sites

Seems like "Voip Phone 1.0" has a small problem with the registration. The phone coming from the IP address "10.255.109.71" never reregisters, the phone coming from 10.255.109.195 has the same problem.

 

Maybe this is because the re-registration interval is shorter than 32 seconds. Just an idea; it should be easy to fix that in the Voip phone software.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...