Bug 73988 - ISDN - first dial attempt fails
Summary: ISDN - first dial attempt fails
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 5.3-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-isdn (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-16 02:50 UTC by Josef M.
Modified: 2006-05-13 14:22 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Josef M. 2004-11-16 02:50:23 UTC 
The *first* dial attempt to my ISP fails with error message: 
"cause 100: Invalid information element contents (Q.850)"
I'm using synchronous PPP with the isp driver.

isndtrace(8) shows that only the first dial attempt includes
a "calling party subaddress" and a "called party subaddress"
field in the message-setup. This indicates that these
fields are causing the problem.

Fix: 

I came up with the following workaround:
Add the following key/value pairs to isdnd.rc(5)

usesubaddr = on    
local-subaddr-dialout = ""
remote-subaddr-dialout = ""

This workaround will suppress the subaddress fields already
the first time.

After a quick look into /usr/src/usr.sbin/i4b/isdnd/msghdl.c
I could imagine, that the variables holding the subaddresses
do not get initialized.
How-To-Repeat:       Restart isdnd(8). Trigger an automatic dial attempt.
e.g. ping www.freebsd.org
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2005-06-07 19:03:48 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-isdn

Over to ISDN Mailinglist
Comment 2 hm freebsd_committer freebsd_triage 2006-05-13 14:17:45 UTC 
State Changed
From-To: open->closed

The fix mentioned in the PR seems to be already the right one 
for this problem. Further evaluation of this problem is not 
possible since ISDN subaddressing is not available here.