search for: pri_facil

...and why it's not displaying. I am tracking this down to "Presentation prohibited of network provided number" even though the Caller doesn't use *67 and even though they haven't asked their provider to block their CLID for outbound. I want to make a modification to q931.c or pri_facility (whichever responsible) to ignore the request from the network to prohibit CLID and to show it so that I can find out exactly where the problem lies. Can you please tell me which "if" is related to that in q931.c or pri_facility.c? Thanks -------------- next part -------------- An HTM...

Hi, Is Asterisk "fully QSIG-compliant"? I currently have an Alcatel 4400 connected to Asterisk 1.2 and 1.4. Zaptel versions are 1.2.26 and 1.4.11. I am using switchtype=euroisdn and all works fine. However, it seems that Alcatel's latest firmware has dropped support for euroisdn which is really despicable. So now I need to see if I can migrate to QSIG which is supported by

...velopment Team has announced the release of version 1.4.11.2 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes situation where Q.SIG calling name in FACILITY message was not reported to the upper layer: * pri_facility.c: Q.SIG calling name in FACILITY message not reported to the upper layer. Q.SIG can send the CallingName, CalledName, and ConnectedName in stand alone FACILITY messages. If the CallingName was not sent in the SETUP message, the caller id name was not...

...by Asterisk 1.2.13-BRIstuffed-0.3.0-PRE-1w pri debug: 1 Length (57) of 0x38 component is too long 1 !! Invalid DivertingLegInformation2 component received 0x38 This only happens on calls that are forwarded to us, the packet in question seems to contain the RDNIS. I guess this needs some code in pri_facility.c that I'm unable to write right now. Should i file a bug-report abut this at http://bugs.digium.com? Greetings & TIA Andy

...velopment Team has announced the release of version 1.4.11.2 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes situation where Q.SIG calling name in FACILITY message was not reported to the upper layer: * pri_facility.c: Q.SIG calling name in FACILITY message not reported to the upper layer. Q.SIG can send the CallingName, CalledName, and ConnectedName in stand alone FACILITY messages. If the CallingName was not sent in the SETUP message, the caller id name was not...

Hi everyone, I was referred to this mailing list by Richard Mudgett regarding the following thread on Issue Tracker as it's a feature request and not a bug:https://issues.asterisk.org/jira/browse/PRI-170 We've got a Nortel BCM (actually 2 BCM50s and 1 BCM400)... all showing the same problem. When a call comes in the number shows up OK but the name does not. In looking at the ISDN messages

...transfer to "no" and all worries gone. Thanks for the input everyone. -Bruce On Mon, Apr 12, 2010 at 10:10 PM, bruce bruce <bruceb444 at gmail.com> wrote: > Futher check into the PRI debug I am seeing this which actually relates to > TBCT and AOC-E error in /usr/src/libpri/pri_facility.c: > > > Message type: FACILITY (98) > > [1c 14 91 a1 11 02 01 06 06 07 2a 86 48 ce 15 00 08 30 03 02 01 03] > > Facility (len=22, codeset=0) [ 0x91, 0xA1, 0x11, 0x02, 0x01, 0x06, 0x06, > 0x07, '*', 0x86, 'H', 0xCE, 0x15, 0x00, 0x08, '0', 0x03, 0x0...