[Home]

Summary:ASTERISK-01521: [request] Full support of SIP 484 "incomplete address"
Reporter:mustdie (mustdie)Labels:
Date Opened:2004-05-02 19:42:14Date Closed:2004-09-25 02:48:26
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) sip.txt
Description:Some of IP phone manufactures (In our case all product line of Grandstream) supports "early dialing" by processing SIP 484 reply message &ASTERISK-7999;address incomplete". Our sip implementation simply does not support that regardless to dial plan. Please see SIP debug attached. And SIP RFC section 7.4.21.  
Comments:By: twisted (twisted) 2004-05-02 21:47:05

According to the sip debugs, we are indeed reporting back the 484 Address Incomplete....  What is the actual problem here?  I don't think Grandstreams' implementation of Early dial is complete, as if we send the 484 to the grandstream, the grandstream should continue to try to invite until we have a complete address.  if the GS is failing to retry, I hardly see why that's our fault.

By: mustdie (mustdie) 2004-05-02 22:27:38

Problem, that I can't match any extension if it's longer then 2 digits. If you will look at my sip debug, you will found that I was trying to dial 134.
exten => _134,.... was defined as very first line in my dial plan, and it didn't worked.
When I've changed it to exten => _13,... it worked perfectly. I don' think this problem is related to Grandstream, because I do have an information that it works fine with other sip proxies.

edited on: 05-02-04 21:40

By: Mark Spencer (markster) 2004-05-02 23:11:29

Looking more closely on your debug, the grandstream is not re-trying after receiving the 407 Proxy Authorization request.  Do you have any explanation, or am I simply misreading the debug?

By: Mark Spencer (markster) 2004-05-03 16:02:18

This is a bug in the grandstream, because it fails to attempt another call after the second digit with authentication.  However, we've added the ability to say "insecure=very" in a friend declaration and thus it will not request authentication from a peer who has registered with us.  As the name suggests, this is not considered particularly secure.