keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
  1. Forum
  3. Telephony Cards Support
  5. D110/210/410 Series
  7. DE210E : missing digits on called party id on PRI level
× Questions about D110/210/410 T1/E1/J1 PRI Cards

DE210E : missing digits on called party id on PRI level

12 years 5 months ago #7552 by fiesch
Hi

i do have an issue with a DE210E card connected to a german E1 line.
On Lines that have noise on them which are calling the machine's PRI line, there are two effects visible:


Fax messages, if accepted, get dropped in the middle of transmission (presumably due to high noise)

The much more important problem: On incoming calls, the called party id is missing digits.
Assuming that the base number is XXXXXX 0, the called number is XXXXXX 9552 - then the span receives XXXXXX 95 as the called number (digits '5' and '2' missing).
This is also visible at the pri level:
TEI: 0 State 7(Multi-frame established)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < V(A)=0, V(S)=0, V(R)=0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < T200_id=0, N200=3, T203_id=16384
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [ 02 01 00 00 08 02 00 2c 05 04 03 90 90 a3 18 03 a1 83 89 1e 02 80 83 6c 0c 21 81 38 39 33 31 36 30 39 38 34 33 70 09 c1 33 35 36 33 36 33 39 35 ]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Informational frame:
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < SAPI: 00  C/R: 1 EA: 0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <  TEI: 000        EA: 1
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < N(S): 000   0: 0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < N(R): 000   P: 0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < 44 bytes of data
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Protocol Discriminator: Q.931 (8)  len=44
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < TEI=0 Call Ref: len= 2 (reference 44/0x2C) (Sent from originator)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Message Type: SETUP (5)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [04 03 90 90 a3]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Bearer Capability (len= 5) [ Ext: 1  Coding-Std: 0  Info transfer capability: 3.1kHz audio (16)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                              Ext: 1  Trans mode/rate: 64kbps, circuit-mode (16)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                                User information layer 1: A-Law (35)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [18 03 a1 83 89]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Channel ID (len= 5) [ Ext: 1  IntID: Implicit  Other(PRI)  Spare: 0  Preferred  Dchan: 0
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                       ChanSel: As indicated in following octets
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                       Ext: 1  Coding: 0  Number Specified  Channel Type: 3
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                       Ext: 1  Channel: 9 Type: CPE]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [1e 02 80 83]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)  0: 0  Location: User (0)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                               Ext: 1  Progress Description: Calling equipment is non-ISDN. (3) ]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [6c 0c 21 81 38 39 33 31 36 30 39 38 34 33]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Calling Number (len=14) [ Ext: 0  TON: National Number (2)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 <                           Presentation: Presentation permitted, user number passed network screening (1)  'YYYYYYYYYYY' ]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < [70 09 c1 33 35 36 33 36 33 39 35]
[Nov  9 21:59:37] VERBOSE[19850] chan_dahdi.c: PRI Span: 2 < Called Number (len=11) [ Ext: 1  TON: Subscriber Number (4)  NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)  'XXXXXX95' ]

This affects about 5%-8% of the calls handled alles the rest is handled fine, unfortunately these are one of our customer's biggest clients so this really is a problem.
The E1 Line itsself is OK as when connected to a legacy swyx PBX with a cologne chip PRI card works fine (including the lines making problems on asterisk)

Software versions:
CentOS 2.6.18
LibPRI 1.4.12
DAHDI(-complete) 2.4.1
Asterisk 1.8.8

Libpri, dahdi, asterisk compiled from digium source

configs:

system.conf

# Autogenerated by /usr/sbin/dahdi_genconf on Tue Nov 8 20:24:44 2011
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4 ClockSource
span=1,1,1,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
#echocanceller=mg2,1-15,17-31

# Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" HDB3/CCS/CRC4 RED
span=2,2,1,ccs,hdb3,crc4
# termtype: te
bchan=32-46,48-62
dchan=47
#echocanceller=mg2,32-46,48-62

# Global data

loadzone = de
defaultzone = de


chan_dahdi_groups.conf (über dahdi-modul freepbx)
; [span_1]
signalling=pri_cpe
switchtype=euroisdn
pridialplan=national
prilocaldialplan=national
group=0
context=from-pstn
channel=1-15,17-31

; [span_2]
signalling=pri_cpe
switchtype=euroisdn
pridialplan=unknown
prilocaldialplan=unknown
group=0
context=from-pstn
channel=32-46,48-62

chan_dahdi_general_custom.conf
internationalprefix = 00
nationalprefix = 0
localprefix = 089
unknownprefix 0
priindication = outofband
usecallerid = yes
callerid = asreceived
usecallingpres=yes

The cable used is self-made, short circuit free and has a resistance of 0.3 to 0.4 ohms.


any ideas on this?
12 years 5 months ago #7557 by tim.june
Please try a lower version of asterisk first, maybe 1.8.5.0,the latest version of asterisk has not been test yet, we will figure it out soon.
Email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Skype: tim.jjune
12 years 5 months ago #7561 by fiesch
Ok i will try that, thank you.

From the trace above i had the impression that this was at the libpri level of things
12 years 5 months ago #7562 by fiesch
Ok, tested with 1.8.5.0, exact same results
12 years 5 months ago #7634 by fiesch
Just to end this tragedy of a support forum entry - the solution is adding

overlapdial=yes
and
immediate=no

to chan_dahdi_groups.conf.
  1. Forum
  3. Telephony Cards Support
  5. D110/210/410 Series
  7. DE210E : missing digits on called party id on PRI level
Time to create page: 0.040 seconds
Powered by Kunena Forum