Discussion:
CAPI Call Deflect Facility Message
(too old to reply)
S***@gmail.com
2006-06-13 10:42:39 UTC
Permalink
Hi all,

I'm using and Eicon BRI with CAPI 2.0. I have writen code to use the
call deflect facility.
As soon as I get a connect indication, I send a facility request for
CD.

I'm passing the Facility Request Parameter as a byte array as follows:

byParam[0] = 0x0C; //length
byParam[1] = 0x0D; //facility selector lo byte
byParam[2] = 0x00; //facility selector hi byte
byParam[3] = 0x01; //presentation allowed
byParam[4] = 0x00; //presentation allowed
byParam[5] = 0x00; //type of facility party number
byParam[6] = 0x00; //type of number
byParam[7] = 0x00; //presentation and screening indicator
byParam[8] = 0x03; //digits
byParam[9] = 0x01; //digits
byParam[10] =0x00; //digits
byParam[11] = 0x80; //deflected-to Subaddress
byParam[12] = 0x80; //deflected-to Subaddress

I dont get a facility conf from the driver.
Could someone tell me where i'm going wrong
Werner Henze
2006-06-13 19:51:26 UTC
Permalink
Hi!
Post by S***@gmail.com
I dont get a facility conf from the driver.
Could someone tell me where i'm going wrong
Without looking at your coded message: what does
CAPI_PUT_MESSAGE return?

Ciao,
Werner...
--
PGP 8 available
http://home.arcor.de/werner.henze
S***@gmail.com
2006-06-14 07:42:53 UTC
Permalink
It returns 0
Werner Henze
2006-06-14 16:14:44 UTC
Permalink
Hi!

In my opinion the driver must reject the message during CAPI_PUT_MESSAGE
or must send a _CONF back. Anything else should be a CAPI error, I assume.

If I look at your coding in more detail, I think I can see the error.
You only code the length of the outermost struct. Why don't you precede
inner structs with their corresponding length?

Ciao,
Werner...
--
PGP 8 available
http://home.arcor.de/werner.henze
mm
2006-06-17 05:41:51 UTC
Permalink
Hi Sune;

As Werner suggested your facility request parameter has a few flaws.

The following should be a full valid Call Deflection Message. It
deflects to no 310.

1E 00 01 00 80 80 01 00
01 01 00 00 03 00 0F 0D
00 0C 01 00 06 01 00 80
33 31 30 02 80 50

I.e. one additional bit you did wrong was to use 0x03, 0x01, 0x00 for
the phone number instead of the IA5 characters. You might want to have
a look at Q.931 for more details, what a "called party number" is.

(Hint: when capi sends i.e. a "called party number" byte array it chops
off the first two bytes from the Q.931 document)

Hope that helped

Michael
Post by S***@gmail.com
Hi all,
I'm using and Eicon BRI with CAPI 2.0. I have writen code to use the
call deflect facility.
As soon as I get a connect indication, I send a facility request for
CD.
byParam[0] = 0x0C; //length
byParam[1] = 0x0D; //facility selector lo byte
byParam[2] = 0x00; //facility selector hi byte
byParam[3] = 0x01; //presentation allowed
byParam[4] = 0x00; //presentation allowed
byParam[5] = 0x00; //type of facility party number
byParam[6] = 0x00; //type of number
byParam[7] = 0x00; //presentation and screening indicator
byParam[8] = 0x03; //digits
byParam[9] = 0x01; //digits
byParam[10] =0x00; //digits
byParam[11] = 0x80; //deflected-to Subaddress
byParam[12] = 0x80; //deflected-to Subaddress
I dont get a facility conf from the driver.
Could someone tell me where i'm going wrong
Loading...