Currently we are using FreePBX 2.11.043 in a series of Radio Stations. Our contest Ques are periodically full and our local “Telus Mobility” people are telling us that our PBX is not sending a proper busy code to their system.
Here is what our current configuration is sending:
Event 10 15/10/23 11:25:47 TEI 0
08 Q.931 Call Control Message
Call Reference Value Dest 239
M 01 Message Type ALERTING
I 1E Progress Indicator Length= 2
81 Coding Standard CCITT
Location Local Private Network
88 Value In-band Information/Pattern Avail
Raw Hex Data
08 02 80 EF 01 1E 02 81 88
Event 11 15/10/23 11:25:47 TEI 0
08 Q.931 Call Control Message
Call Reference Value Dest 239
M 45 Message Type DISCONNECT
I 08 Cause Length = 2
81 Coding Standard CCITT
Location Local Private Network
91 Class Normal Event
Value #17, User Busy
and this is what they are expecting (as shown from another system):
==> 00:06:55:13.41 (CM Time: 11:06:32:18.95).
==> Q931: SETUP: to S[7040] L[1,474,0] E[37,473,0] SPA[----]
CR: 0,15 F5
BC: speech
64 kbit/s
circuit mode
mu-law speech
CID: 18
LENGTH: 03
Channel Selection Info: As Indicated in Following Octets
D-Channel Indicator: D-Channel NOT indicated
Preferred/Exclusive: Exclusive
Interface type = primary rate
Interface Identifier: IID Implicitly Identified
Channel Type: B - Channel Units (3).
Number Map: Channel is indicated by the number following.
Coding Standard: CCITT
Channel Number = 1
FAC:
Protocol Profile: Networking Extensions
8B 01 00 A1 0F 02 01 5D 06 07 2A 86 48 CE 15 00
04 0A 01 00
Interpretation Component
Interpretation Value: Discard
Invoke Component
Invoke Identifier Tag: 2
Invoke identifier: 93
Operation Component
Operation value: informationFollowing
PI: public_network_serving_local_user
origination_address_is_non_ISDN
CGN: e164
national_number
network_provided
presentation_allowed
6042770650
CDN: e164
national_number
604xxxxxxx
<== 00:06:55:13.46 (CM Time: 11:06:32:19.00).
<== Q931: REL COM: from S[7040] L[1,474,0] E[37,473,0] SPA[----]
CR: 1,15 F5
CSE: user
user_busy
Can anyone give me a hand on how to rectify my problem?
I do have a sleazy work around for this but it is not a good one… it involves a failover for the que to a “busy message and hangup”… not polite…