caller ID and implementer's guide
Paul Long
Plong at SMITHMICRO.COM
Thu May 13 18:25:34 EDT 1999
Chip,
Funny you should ask. In my first response to Glen, I said that we clear the
call, but just a few minutes ago I took another look at the code and found
that we completely ignore the calling party number IE in SETUP. Skip right
over the sucker. I must have been looking at how we handle the octet-3
extension bit for another IE, e.g., bearer capability (even Q.931 requires it
to always be 1).
While it turns out that we accept a call regardless of whether the extension
bit under discussion is set, I still stand by my assertion that an EP cannot
send a SETUP message to a v1 or v2 EP with the extension bit of octet 3 set to
0 and octet 3a present. I happen to know what my implementation does, and the
impact is minimal, but there are bound to be implementations out there
that--through no fault of their own--will in effect become "broken" if we
decide that this bit can be set to 0 and this octet can be present after all.
Paul Long
Smith Micro Software, Inc.
-----Original Message-----
From: Chip Sharp [SMTP:chsharp at CISCO.COM]
Sent: Thursday, May 13, 1999 3:49 PM
To: ITU-SG16 at MAILBAG.INTEL.COM
Subject: Re: caller ID and implementer's guide
What does your implementation do if it receives a "0" in the Extension
field of Octet 3?
Chip
More information about the sg16-avd
mailing list