Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
I've now twigged that this is an SS7 flag and is being set in our switch as a result of * passing the Network provided screening indicator to a value that is interpreted as untrusted. Is there a simple way of changing the default value for this? At 16:22 30/01/04, you wrote: I am having a little bit of a problem with BT rejecting my callerid values as they are prefixed by hex b. This indicates that the caller id is user provided and not verified. Does anyone know how I can control where this appears in the cli? The purpose of the separator is described below: 1 - PNO 006 section 2.4.19 c note states that the hex b denotes an address separator, to separate the part which is network provided from that which is user provided - This means that it separates the extension number from the rest of the number. 2 - PNO008 section 22.1.3.3 states that the hex b dependant on its position, denotes whether the screening indicator is user provided not verified, network provided or user provided verified and passed. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
I missed your earlier message, but to try and help: a) You are correct, the hex 'b' usage is only valid in the UK specific BT IUP SS#7 interconnect protocol and therefore is nothing to do with PRI usage whatsoever (or indeed ISUP SS#7). b) In q931.c these various flags can be set for outbound CLI (caller id), from user provided not verified, user provider verified, user provided verfication failed, and network provided. c) BT however will only accept CLI that you are authorised to send - whatever the state of the flags, this means that you can only send CLI that matches numbers that have been allocated to your PRI. If you are trying to do otherwise this will always fail. Linus - Original Message - From: bam [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 12:02 PM Subject: Re: [Asterisk-Users] Address Separator hex b causes callerid rejection I've now twigged that this is an SS7 flag and is being set in our switch as a result of * passing the Network provided screening indicator to a value that is interpreted as untrusted. Is there a simple way of changing the default value for this? At 16:22 30/01/04, you wrote: I am having a little bit of a problem with BT rejecting my callerid values as they are prefixed by hex b. This indicates that the caller id is user provided and not verified. Does anyone know how I can control where this appears in the cli? The purpose of the separator is described below: 1 - PNO 006 section 2.4.19 c note states that the hex b denotes an address separator, to separate the part which is network provided from that which is user provided - This means that it separates the extension number from the rest of the number. 2 - PNO008 section 22.1.3.3 states that the hex b dependant on its position, denotes whether the screening indicator is user provided not verified, network provided or user provided verified and passed. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
The problem is that the ISDN call to our switch has the screening indicator set to untrusted, to the switch sticks 0xb on the front of the CLI. BT then drop the CLI altogether. So I need to find a way of fiddling with the * presentation. At 12:29 02/02/04, you wrote: I missed your earlier message, but to try and help: a) You are correct, the hex 'b' usage is only valid in the UK specific BT IUP SS#7 interconnect protocol and therefore is nothing to do with PRI usage whatsoever (or indeed ISUP SS#7). b) In q931.c these various flags can be set for outbound CLI (caller id), from user provided not verified, user provider verified, user provided verfication failed, and network provided. c) BT however will only accept CLI that you are authorised to send - whatever the state of the flags, this means that you can only send CLI that matches numbers that have been allocated to your PRI. If you are trying to do otherwise this will always fail. Linus ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
The problem is that the ISDN call to our switch has the screening indicator set to untrusted, to the switch sticks 0xb on the front of the CLI. BT then drop the CLI altogether. So I need to find a way of fiddling with the * presentation. Ahhh. so you have an interconnect switch then I take it! You need to set the q931.c value - PRES_ALLOWED_NETWORK_NUMBER which has a value of '3'. I think, although I've never tried this, you can actually call the application CallingPres with the value of 3 before making an outbound call. CallingPres(3) I think should do it - someone else might be able to advise better. Linus ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
The problem is that the ISDN call to our switch has the screening indicator set to untrusted, to the switch sticks 0xb on the front of the CLI. BT then drop the CLI altogether. Actually, just as a point, the 0xb doesnt mean 'untrusted' as such, it just means user provided. I'd be interested if you'd like to dial 0870 068 9001 and let me know the date and time of the call to see if we see the CLI you are trying to pass. Linus ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
We do indeed, no one to blame :-( CallerPres(3) does the business, thank you very much. Is there a list of all the applications somewhere? I've been looking in asterisk/apps/ and can't find CallerPres. all the best, Brian At 13:41 02/02/04, you wrote: Ahhh. so you have an interconnect switch then I take it! You need to set the q931.c value - PRES_ALLOWED_NETWORK_NUMBER which has a value of '3'. I think, although I've never tried this, you can actually call the application CallingPres with the value of 3 before making an outbound call. CallingPres(3) I think should do it - someone else might be able to advise better. Linus ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Address Separator hex b causes callerid rejection
show applications in the Asterisk CLI. Then show applicationname On Mon, 2004-02-02 at 11:04, bam wrote: We do indeed, no one to blame :-( CallerPres(3) does the business, thank you very much. Is there a list of all the applications somewhere? I've been looking in asterisk/apps/ and can't find CallerPres. all the best, Brian At 13:41 02/02/04, you wrote: Ahhh. so you have an interconnect switch then I take it! You need to set the q931.c value - PRES_ALLOWED_NETWORK_NUMBER which has a value of '3'. I think, although I've never tried this, you can actually call the application CallingPres with the value of 3 before making an outbound call. CallingPres(3) I think should do it - someone else might be able to advise better. Linus ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Go to http://www.digium.com/index.php?menu=documentation and look at the Unofficial Links section. This section has links to a wide variety of 3rd party Asterisk related pages. My page is the Asterisk Resource Pages. BTEL Consulting 504-899-1387 or 850-484-4545 or 877-677-9643 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Address Separator hex b causes callerid rejection
I am having a little bit of a problem with BT rejecting my callerid values as they are prefixed by hex b. This indicates that the caller id is user provided and not verified. Does anyone know how I can control where this appears in the cli? The purpose of the separator is described below: 1 - PNO 006 section 2.4.19 c note states that the hex b denotes an address separator, to separate the part which is network provided from that which is user provided - This means that it separates the extension number from the rest of the number. 2 - PNO008 section 22.1.3.3 states that the hex b dependant on its position, denotes whether the screening indicator is user provided not verified, network provided or user provided verified and passed. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
