Dial to numbers with letters in it (1234123D, f.e.)

Asterisk Asterisk Support
1

Hello. I’m unable to dial to numbers with letters in it.
TE210P Digium card with two E1 lines in it.

On dial out message:

2 > Message type: SETUP (5) 2 > [04 03 80 90 a3] 2 > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0) 2 > Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16) 2 > Ext: 1 User information layer 1: A-Law (35) 2 > [18 03 a9 83 81] 2 > Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 Exclusive Dchan: 0 2 > ChanSel: Reserved 2 > Ext: 1 Coding: 0 Number Specified Channel Type: 3 2 > Ext: 1 Channel: 1 ] 2 > [6c 0c 21 83 32 31 33 32 31 33 {skip} ] 2 > Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) 2 > Presentation: Presentation allowed of network provided number (3) '213213{skip}' ] 2 > [70 0d 80 {skip} 30 30 31 44] 2 > Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) '{skip}001D' ]
Got momentally reject:

2 < Call Ref: len= 2 (reference 3/0x3) (Terminator) 2 < Message type: RELEASE COMPLETE (90) 2 < [08 02 80 9c] 2 < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: User (0) 2 < Ext: 1 Cause: Invalid number format (28), class = Normal Event (1) ] 2 -- Processing IE 8 (cs0, Cause)
Provider says, that his trace shows no attempt to dial that number.

zaptel.conf:

#Configuration for EuroISDN (E1) span=1,0,0,ccs,hdb3,crc4 span=2,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 bchan=32-46,48-62 dchan=47 loadzone = de defaultzone=de
zapata.conf:

[code][channels]
switchtype=euroisdn
pridialplan=unknown
prilocaldialplan=unknown
signalling=pri_cpe
usecallerid=yes
context => zap_in
channel => 32-46,48-62

irrelevant rest[/code]

What’s wrong and where? :frowning:

2

have tried all variants of pridialplan:
unknown – std numbers OK, letters FAIL
national – std numbers FAIL, letters FAIL
local – std numbers OK, letters FAIL
private – std numbers OK, letters FAIL
international – std numbers FAIL, letters FAIL
dynamic – std numbers FAIL, letters FAIL

What’s wrong? I really need to dial that numbers.

3

I’m not familiar with QSIG, although the traces suggest that it is using ASCII, rather than telephony BCD, however, in my long past dealings with System X, I am pretty sure that the SS7 Telephony User Part only supports four bits per digit, so I wouldn’t expect an ASCII D to get across the public network. Moreover, I’m not aware of any use of the a, b, c, d digits.

So, firstly, by D do you mean DTMF D, or ASCII D?

Secondly, what is supposed to be responding to this D?

As to the different number format modes, I think you need to omit the initial 0 (or whatever is used in your country) when providing a National Number Dialled number.

4

This wouldn’t allow the sending of ASCII D, and I doubt it actually allows a, b, c, d, * or # either. (RFC 2916 doesn’t permit them when mapping to DNS names.)

The 44 is an ASCII D. Whether this means literally D or the extended BCD d digit, in QSIG, I don’t know.

6

[70 0d 80 {skip} 30 30 31 64]
Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘{skip}001d’ ]

< Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: User (0)
< Ext: 1 Cause: Invalid number format (28), class = Normal Event (1) ]

well, “size doesn’t matter”.
How to call that numbers from asterisk? :frowning:

“D” at end, is a routing firewall to avoid the number would be accessible by any person who does dial the number without d on the end.

7

It looks to me that your service provider is rejecting the D (and you still haven’t explained what you actually mean by D), probably because their network cannot transmit it.

Are you sure that the D should not be sent as a DTMF D, in band, after the service provider has established the call.

PS your traces include the full dialled number.

8

ABCD are the Extensions of Touchtones and they are usually found on Special Test phones (the ones that the Telephone Installers have). As far as I know, these numbers are not used by anyone except maybe the military.

I don’t think ISDN will accept these digits as a dial sequence, and as a previous poster mentioned, perhaps you should send them as DTMF instead of signalling.

Or if Asterisk doesnt support A B C D as DTMF, get a Sound Editor like Cool Edit Pro and Generate the A B C or D and Save them to a Wave File. After your call is answered, play them as a Prompt.

Dave
\

9

Have tried DTMF after number picks up – not works.
That “D” not DTMF, that Hex D in number.

10

Deleted duplicate.

11

There may be terminology problems here and there is a limit on how much time I can spend on this, but when you said you used DTMF, did mean you did something like:

wait(1)
senddtmf(d)

after the Dial application returned?

Note that what you actually sent to the switch was in ASCII, not hex, and a hex d in TBCD corresponds to digit b. TBCD cannot represent digit d as the hex f code is used for something else, see, for example: <http://www.itu.int/ITU-T/asn1/database/itu-t/q/q825/1998/Q825-CDR-ASN1Module.html>. As TBCD is probably used in the public network connection protocols that means you can’t reliably send digit d and to send a TBCD 0xd, you would need to send digit b.

I have a feeling that this question would be better addressed to the support department of the vendor of the equipment you are trying to access.

12

Nope, under “tried DTMF” i mean:
Dial(ZAP/{skip}123,D(d))

Also, I have tried variants
Dial(ZAP/w{skip}123d)
Dial(ZAP/{skip}123wd)
Dial(ZAP/{skip}123dw)
with overlapdial=yes

Well, I have tried
Dial(ZAP/{skip}123b)

[70 0d 80 {skip} 31 32 33 62]
Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘{skip}123b’ ]
and
Dial(ZAP/{skip}123B)

[70 0d 80 {skip} 31 32 33 42]
Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘{skip}123B’ ]
With also no luck.

13 

Provider (In-Telegence) says, that there no setup messages in traces with letters come to his end. So, seems that messages just not comes out from TE210 card!

Provider (In-Telegence) says, that there no setup messages in traces with letters come to his end. So, seems that messages just not comes out from TE210 card!

14

I don’t have the time to follow this further, but it would surprise me if the rejection was coming from the near end. I’d need to research QSIG and the source code to go further.

Have you confirmed with the provider, that their network is actually capable of forwarding digits beyond 0 to 9?

15

Yes, provider also sais –

[quote]ollen die Buchstaben ein Routenschutz sein? Wenn ja, probieren Sie es mal mit einem B oder C. Ein F geht nicht, da das F fur “end of sign” steht.

Ein B oder C sollte aber funktionieren.[/quote]

I.e. we must use “B” to send hexD.
But messages with {skip}123B also doesn’t works, and not seen in providers’ trace.

16

I have tried even
[70 0d 80 {skip} 31 32 33 3b]
Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘{skip}123;’ ]

(note 0x3B as last letter).
Also not works.
And again:
< Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) Spare: 0 Location: User (0)
< Ext: 1 Cause: Invalid number format (28), class = Normal Event (1) ]

Location: User (0)

17

2 > [70 0d 80 {skip} 31 32 33 3d]
2 > Called Number (len=15) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘{skip}123=’ ]

tried such varian (note of “3D” as last letter).
Same result.

18

Looks like problem found: provider found with message tracer, that messages there – so, seems problem not in digium card.
His switch blocks messages just it have arrived, without logging it at all.

Provider doing test on our port config:) Hope, that will helps.
Don’t close post: i’ll post solution and format of number to send, when get it worked right.