603 Decline message as a response to the INVITE

[Edy]

1. Brekeke Product Name and version:
SIP Server, version 2.1

2. Java version:
version 1.6

3. OS type and the version:
Windows 200

4. UA (phone), gateway or other hardware/software involved:
UA - Bria(CounterPath)

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
About Pattern 6

6. Your problem:
The Brekeke SIP Server gets messages from the clients (Bria CounterPath UA client) and forwards them to our SIP Server. The Brekeke performs the authentication process during the client registration.
We have two UA clients with the same configuration but different geographical locations (after NAT).
One of the clients is registered and makes the calls properly but another one registered in the Brekeke SIP Server but for each INVITE message gets the 603 Decline message and the INVITE message is not forwarded to our SIP Server. We are trying to understand the reason for the 603 Decline message for the INVITE message.
Thanks a lot,
Edy

[voipwell.com]

Please remove java 1.6 and install java 1.5.13. I wish Brekeke would put this in big reg letters at the top of every page.

Nick

[Edy]

Please remove java 1.6 and install java 1.5.13. I wish Brekeke would put this in big reg letters at the top of every page.

Nick

Hi Nick,
Acctually the problem is not in the java version.
The SIP client is connected to the Internet through the 3G Mobile phone (as a modem) and in this case, the INVITE body (SDP) contains an additional parameter:
a=alt:1 1 : BYxmad6g dAsopJFq 192.118.11.120:31478 4560that cause the Brekeke SIP server to send the 603 Decline message back to the client.
After a short searching we found out that this parameter is added because of the ICE mechanism. Once we disable it in the client the problem is disappeared.
Our question is whether the Brekeke SIP Server supports the ICE mechanism and in prticular the a=alt parameter.
See the full message below.

Thanks,
Edy


INVITE sip:037678405@213.8.61.45 SIP/2.0
Via: SIP/2.0/UDP 192.118.11.120:31478;branch=z9hG4bK-d8754z-2753d80e16370c51-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:97297626825@192.118.11.120:31478>
To: <sip:037678405@213.8.61.45>
From: "97297626825"<sip:97297626825@213.8.61.45>;tag=f872532d
Call-ID: NDY1MWI2NGMwZTdjMGVmOWJkZGY2ZDBkOGU4NjQwNjI.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: Bria release 2.1.1 stamp 43324
Content-Length: 339

v=0
o=- 2 2 IN IP4 192.118.11.120
s=CounterPath CMC
c=IN IP4 192.118.11.120
t=0 0
m=audio 39951 RTP/AVP 0 8 18 101
a=alt:1 1 : BYxmad6g dAsopJFq 192.118.11.120:31478 4560a=fmtp:18 annexb=yes
a=fmtp:101 0-15
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv
a=x-rtp-session-id:EA68787D219C4425808E9EB9A2DBCE3F

[voipwell.com]

I know there is a problem with the 1.6 java with brekeke pbx, I have not tested sip server only. We use xlite phones with ice turned on with pbx and have no problems. I wonder if java 1.5 has problem with ice also?

Nick

[lakeview]

Hi All,

If the problem is related with the SDP, you may see the message "Invalid SDP" in the Call Logs page.


LV

[lakeview]

Add "net.sip.sdp.a-alt.use=false" in the Configuration > Advanced page.
It will avoid the issue.

LV

[lakeview]

The definition of alt-attribute is
a=alt:<id> <qvalue> <username> <password> <unicast-address> <port>

So
a=alt:1 1 : BYxmad6g dAsopJFq 192.118.11.120:31478 4560 was not well formatted.