WIKI SUPPORT SEARCH LOGIN REGISTER
Brekeke Forum Index » Brekeke SIP Server Forum

Post new topic   Reply to topic
Got SIP response 500 "Internal Server Error" back
Author Message
jfreeman1969
Brekeke Newbie


Joined: 06 Sep 2011
Posts: 1
Location: Birmingham, AL
PostPosted: Tue Sep 06, 2011 1:34 pm    Post subject: Got SIP response 500 "Internal Server Error" back Reply with quote
1. Brekeke Product Name and version: Brekeke SIP Server, 2.4.7.3/286.1

2. Java version: 1.6.0_24

3. OS type and the version: Linux (Centos) 2.6.18-194.32.1.el5

4. UA (phone), gateway or other hardware/software involved: Polycom IP 335 & 450, FreePBX (Asterisk 1.8.5)

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html : Pattern 3

6. Your problem: We have a FreePBX server with Asterisk 1.8. Each extension on the server is logging "-- Got SIP response 500 "Internal Server Error" back from 10.1xx.xx.xx:5060" every few seconds. The error is coming from our Brekeke Server.

SIP Debug shows (on FreepBX Server) :

<--- SIP read from UDP:10.130.33.13:5060 --->
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK187da513
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as2b6117f5
To: <sip:400@10.130.33.13:5060>
Call-ID: 62a7e70a71241a8717d2aec11402173f@10.140.1.13:5060
CSeq: 102 OPTIONS
Server: Brekeke SIP Server rev.286.1
Content-Length: 0

<------------->
--- (8 headers 0 lines) ---

<--- SIP read from UDP:10.130.33.13:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK187da513
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as2b6117f5
To: "Jeanne Bowers" <sip:400@10.130.33.13:5060>;tag=10AD2A7C-99DBC3FB
CSeq: 102 OPTIONS
Call-ID: 62a7e70a71241a8717d2aec11402173f@10.140.1.13:5060
Contact: <sip:400@10.130.33.13:5060>
Record-Route: <sip:10.130.33.13:5060;lr>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Supported: 100rel,replaces,100rel,timer,replaces,norefersub
User-Agent: PolycomSoundPointIP-SPIP_335-UA/3.3.2.0413
Accept-Language: en
Accept: application/sdp,text/plain,message/sipfrag,application/dialog-info+xml
Accept-Encoding: identity
Content-Length: 0

<------------->
--- (15 headers 0 lines) ---
Really destroying SIP dialog '62a7e70a71241a8717d2aec11402173f@10.140.1.13:5060' Method: OPTIONS

<--- SIP read from UDP:10.130.33.13:5060 --->
SUBSCRIBE sip:1@10.140.1.13:5060 SIP/2.0
Via: SIP/2.0/UDP 10.130.33.13:5060;rport;branch=z9hG4bKd795d17abb6165167dd1c-f9c14a06-61e191a6
Via: SIP/2.0/UDP 192.168.1.8;branch=z9hG4bK3b278bd4C65EBF1F;received=96.37.151.22
From: "Celeste" <sip:100@10.140.1.13>;tag=F6CD1A32-63AE3615
To: <sip:1@10.140.1.13>
CSeq: 1 SUBSCRIBE
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
Contact: <sip:100@10.130.33.13:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: message-summary
User-Agent: PolycomSoundPointIP-SPIP_450-UA/3.3.2.0413
Accept-Language: en
Accept: application/simple-message-summary
Max-Forwards: 69
Expires: 3600
P-Behind-NAT: Yes
Record-Route: <sip:10.130.33.13:5060;lr>
Content-Length: 0

<------------->
--- (18 headers 0 lines) ---
Creating new subscription
Sending to 10.130.33.13:5060 (no NAT)
list_route: hop: <sip:10.130.33.13:5060;lr>
Found peer '100' for '100' from 10.130.33.13:5060

<--- Transmitting (no NAT) to 10.130.33.13:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.130.33.13:5060;branch=z9hG4bKd795d17abb6165167dd1c-f9c14a06-61e191a6;received=10.130.33.13;rport=5060
Via: SIP/2.0/UDP 192.168.1.8;branch=z9hG4bK3b278bd4C65EBF1F;received=96.37.151.22
From: "Celeste" <sip:100@10.140.1.13>;tag=F6CD1A32-63AE3615
To: <sip:1@10.140.1.13>;tag=as3cf26a02
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
CSeq: 1 SUBSCRIBE
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="4fcf8aa6"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '69f08f66-88a62ad9-cf9b1d68@192.168.1.8' in 6400 ms (Method: SUBSCRIBE)

<--- SIP read from UDP:10.130.33.13:5060 --->
SUBSCRIBE sip:1@10.140.1.13:5060 SIP/2.0
Via: SIP/2.0/UDP 10.130.33.13:5060;rport;branch=z9hG4bK97e65be7b47005167dd1c-f9c14a06-9be5ade8
Via: SIP/2.0/UDP 192.168.1.8;branch=z9hG4bK8a068bc345C22A5A;received=96.37.151.22
From: "Celeste" <sip:100@10.140.1.13>;tag=F6CD1A32-63AE3615
To: <sip:1@10.140.1.13>
CSeq: 2 SUBSCRIBE
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
Contact: <sip:100@10.130.33.13:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
Event: message-summary
User-Agent: PolycomSoundPointIP-SPIP_450-UA/3.3.2.0413
Accept-Language: en
Accept: application/simple-message-summary
Authorization: Digest username="100", realm="asterisk", nonce="4fcf8aa6", uri="sip:1@10.140.1.13:5060", response="63fdd39d82bf746c2d9459e71a2232e2", algorithm=MD5
Max-Forwards: 69
Expires: 3600
P-Behind-NAT: Yes
Record-Route: <sip:10.130.33.13:5060;lr>
Content-Length: 0

<------------->
--- (19 headers 0 lines) ---
Creating new subscription
Sending to 10.130.33.13:5060 (no NAT)
Found peer '100' for '100' from 10.130.33.13:5060
Scheduling destruction of SIP dialog '69f08f66-88a62ad9-cf9b1d68@192.168.1.8' in 3610000 ms (Method: SUBSCRIBE)

<--- Transmitting (no NAT) to 10.130.33.13:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.130.33.13:5060;branch=z9hG4bK97e65be7b47005167dd1c-f9c14a06-9be5ade8;received=10.130.33.13;rport=5060
Via: SIP/2.0/UDP 192.168.1.8;branch=z9hG4bK8a068bc345C22A5A;received=96.37.151.22
Record-Route: <sip:10.130.33.13:5060;lr>
From: "Celeste" <sip:100@10.140.1.13>;tag=F6CD1A32-63AE3615
To: <sip:1@10.140.1.13>;tag=as3cf26a02
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
CSeq: 2 SUBSCRIBE
Server: FPBX-2.9.0(1.8.5.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 3600
Contact: <sip:1@10.140.1.13:5060>;expires=3600
Content-Length: 0


<------------>
Reliably Transmitting (no NAT) to 10.130.33.13:5060:
NOTIFY sip:100@10.130.33.13:5060 SIP/2.0
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK7396e82e
Max-Forwards: 70
Route: <sip:10.130.33.13:5060;lr>
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as3cf26a02
To: <sip:100@10.130.33.13:5060>;tag=F6CD1A32-63AE3615
Contact: <sip:Unknown@10.140.1.13:5060>
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
CSeq: 102 NOTIFY
User-Agent: FPBX-2.9.0(1.8.5.0)
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 91

Messages-Waiting: no
Message-Account: sip:*97@10.140.1.13:5060
Voice-Message: 0/0 (0/0)

---
Retransmitting #1 (no NAT) to 10.130.33.13:5060:
NOTIFY sip:100@10.130.33.13:5060 SIP/2.0
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK7396e82e
Max-Forwards: 70
Route: <sip:10.130.33.13:5060;lr>
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as3cf26a02
To: <sip:100@10.130.33.13:5060>;tag=F6CD1A32-63AE3615
Contact: <sip:Unknown@10.140.1.13:5060>
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
CSeq: 102 NOTIFY
User-Agent: FPBX-2.9.0(1.8.5.0)
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 91

Messages-Waiting: no
Message-Account: sip:*97@10.140.1.13:5060
Voice-Message: 0/0 (0/0)

---

<--- SIP read from UDP:10.130.33.13:5060 --->
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK7396e82e
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as3cf26a02
To: <sip:100@10.130.33.13:5060>;tag=F6CD1A32-63AE3615
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
CSeq: 102 NOTIFY
Event: message-summary
Server: Brekeke SIP Server rev.286.1
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---

<--- SIP read from UDP:10.130.33.13:5060 --->
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 10.140.1.13:5060;branch=z9hG4bK7396e82e
From: "Unknown" <sip:Unknown@10.140.1.13>;tag=as3cf26a02
To: <sip:100@10.130.33.13:5060>;tag=F6CD1A32-63AE3615
CSeq: 102 NOTIFY
Call-ID: 69f08f66-88a62ad9-cf9b1d68@192.168.1.8
Record-Route: <sip:10.130.33.13:5060;lr>
Event: message-summary
User-Agent: PolycomSoundPointIP-SPIP_450-UA/3.3.2.0413
Accept-Language: en
Content-Length: 0

<------------->
--- (11 headers 0 lines) ---
-- Got SIP response 500 "Internal Server Error" back from 10.130.33.13:5060
Really destroying SIP dialog '69f08f66-88a62ad9-cf9b1d68@192.168.1.8' Method: SUBSCRIBE

___
First of all, How can I look into the logs of Brekeke and figure out why I am getting this error?

Second, it looks like the error has something to do with turning the voicemail light on/off on the polycom phones.

Any ideas?
_________________
Jeff Freeman
Back to top
View user's profile
hope
Brekeke Master Guru


Joined: 15 Jan 2008
Posts: 862

PostPosted: Tue Sep 06, 2011 2:56 pm    Post subject: Reply with quote
if set correct IP for voicemail server at phone side,brekeke sip server will forward the subscribe to this ip.
or use dial plan at brekeke sip server to forward subscribe requests to correct servers which handle these requests.
Back to top
View user's profile
ambrosio
Brekeke Master Guru


Joined: 27 Mar 2008
Posts: 215

PostPosted: Tue Sep 06, 2011 4:08 pm    Post subject: Reply with quote
See the "500 Internal Server Error" response packet.

>> User-Agent: PolycomSoundPointIP-SPIP_450-UA/3.3.2.0413

It seems Polycom device sent the 500 message.


Does FreePBX send NOTIFY packet just after it receives SUBSCRIBE?
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    Brekeke Forum Index » Brekeke SIP Server Forum All times are GMT - 7 Hours
Page 1 of 1