Asterisk, Requested Transfer Capability: 0x00 – SPEECH

Home » Asterisk Users » Asterisk, Requested Transfer Capability: 0x00 – SPEECH
Asterisk Users 5 Comments

Hello, I’m having issues connecting throu PRI with the following error “Requested transfer capability: 0x00 – SPEECH”

Below are the logs:

== Using SIP RTP CoS mark 5
— Executing [97052660@voipphones:1] Set(“SIP/4856-00000003”,
“CALLERID(num)=xxxxxxxxx”) in new stack
— Executing [97052660@voipphones:2] Dial(“SIP/4856-00000003”,
“dahdi/g1/97052660”) in new stack
— Requested transfer capability: 0x00 – SPEECH
— Called dahdi/g1/97052660
— Span 1: Channel 0/1 got hangup, cause 27
— DAHDI/i1/97052660-4 is circuit-busy
— Hungup ‘DAHDI/i1/97052660-4’
== Everyone is busy/congested at this time (1:0/1/0)
— Auto fallthrough, channel ‘SIP/4856-00000003’ status is ‘CONGESTION’

/etc/asterisk Chan_dahdi.conf

; PRI to Telco callerid=asreceived context=fromtelco switchtype=national signalling=pri_cpe group=1
channel => 1-23

; pri to PBX
context=frompbx switchtype=national signalling=pri_net group=2
channel => 25-47

In /etc/dahdi Modules


/etc/dahdi System.conf

# PRI to Telco span=1,1,0,esf,b8zs bchan=1-23

# PRI to PBX
span=2,0,0,esf,b8zs bchan%-47

Any suggestoins are welcome!
Thanks in advance!

5 thoughts on - Asterisk, Requested Transfer Capability: 0x00 – SPEECH

  • You are dialing a 8 digit number. Why?


    Cause No. 27 – destination out of order. This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term “not functioning correctly” indicates that a signal message was unable to be delivered to the remote party; e.g., a physical layer or data link layer failure at the remote party or user equipment off-line.

  • You need to modify your dialplan to change 9xxxxxxx to 1aaaxxxxxxx. I think most U.S. SIP providers want a 10 digit number.

    —–Original Message—