AVAYA CM R13 - Modular Messaging QSIG Integration 1

[mrcom12]

Hi I have an issue with getting the integration working on AVAYA CM and Modular Messaging.

I have AVAYA CM R013i.01.4.642.1
Modular Messaging 3.1

Connection is QSIG via DS1 board.

The issue only occurs when calling a station which is on cover to the MM the MM is not recognising the extension so does not play back the proper message, but when you dial directly to MM from that station it is able to recognise the station I am calling from.

Any ideas, have followed the integration notes CN88004 but no joy.

thanks

 

[rgtrgt]

send us a paste of the hunt group

 

[mrcom12]

Hi I have pasted Hunt, Trunk Grp, Sys Feat, Signal

display hunt-group 50 Page 1 of 10
HUNT GROUP

Group Number: 50 ACD? n
Group Name: Modular Messaging Queue? n
Group Extension: 4141 Vector? n
Group Type: ucd-mia Coverage Path:
TN: 1 Night Service Destination:
COR: 1 MM Early Answer? n
Security Code: Local Agent Preference? n
ISDN Caller Display: grp-name
HUNT GROUP

LWC Reception: none

Message Center: qsig-mwi
Send Reroute Request: n
Voice Mail Number: 4574141
Routing Digits (e.g. AAR/ARS Access Code): *22 Provide Ringback? n
TSC per MWI Interrogation? n

HUNT GROUP
Group Number: 50 Group Extension: 4141 Group Type: ucd-mia
Member Range Allowed: 1 - 200 Administered Members (min/max): 0 /0
Total Administered Members: 0
GROUP MEMBER ASSIGNMENTS
Ext Name (24 characters) Ext Name (24 characters)
1 : 14 :
2 : 15 :
3 : 16 :
4 : 17 :
5 : 18 :
6 : 19 :
7 : 20 :
8 : 21 :
9 : 22 :
10 : 23 :
11 : 24 :
12 : 25 :
13 : 26 :

display system-parameters features

ISDN PARAMETERS

Send Non-ISDN Trunk Group Name as Connected Name? n
Display Connected Name/Number for ISDN DCS Calls? y
Send ISDN Trunk Group Name on Tandem Calls? n
Send Custom Messages Through QSIG? n

QSIG TSC Extension: 4050
MWI - Number of Digits Per Voice Mail Subscriber: 4
Feature Plus Ext:
National CPN Prefix:
International CPN Prefix:
Pass Prefixed CPN to ASAI? n
Unknown Numbers Considered Internal for AUDIX? n
USNI Calling Name for Outgoing Calls? n
Path Replacement with Measurements? y
QSIG Path Replacement Extension: 4051
Path Replace While in Queue/Vectoring? n


display feature-access-codes


Auto Alternate Routing (AAR) Access Code: *22

display trunk-group 10 Page 1 of 11
TRUNK GROUP

Group Number: 10 Group Type: isdn CDR Reports: y
Group Name: Mod Mess QSIG COR: 1 TN: 1 TAC: 89
Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4 Group Type: isdn

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added? n
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format: unk-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n
display trunk-group 10 Page 3 of 11
TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member: 29
Send Name: y Send Calling Number: y
Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: unk-pvt
Outgoing Channel ID Encoding: exclusive UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y
Hold/Unhold Notifications? y
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

Apply Local Ringback? n

Network (Japan) Needs Connect Before Disconnect? n
QSIG TRUNK GROUP OPTIONS




Diversion by Reroute? y
Path Replacement? y
Path Replacement with Retention? n
Path Replacement Method: better-route
SBS? n
Display Forwarding Party Name? y
Character Set for QSIG Name: eurofont

SIGNALING GROUP

Group Number: 10 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 29
Primary D-Channel: 01B0116 Max number of CA TSC: 29
Trunk Group for NCA TSC: 10
Trunk Group for Channel Selection: 10 X-Mobility/Wireless Type: NONE
Supplementary Service Protocol: b Network Call Transfer? n



Thanks

 

[rgtrgt]

everything look correct to me, try putting the extension in front of the name

 

[MaxEMEA]

MM uses the QSIG DL2 (Divert Leg Info 2)message to decide what the correct mailbox is and where it came from. Either CM is sending the wrong info or MM is not reading the DL2 message properly.
Do you have a trace of a bad call?

 

[mrcom12]

Hi thanks for the input everybody, this has now been resolved by AVAYA Tier 4 intervention who had to write some code.

Thank you

 

[phoneguy2286]

you wouldn't happen to have a person at AVAYA who worked on this issue would you?

we are in exactly the same situation, and in a hospital environment and would like to get this fixed asap.

thanks,
Gene
--bprophet-at-gmail-dot-com--

 

[ilikeavaya]

can't you use the private numbering to ensure the correct digits are being sent over the q-sig tie

 

[Mitch672]

ilikeavaya is correct, you need to do a "change private 0" and make sure that all your DID's are defined that are being sent to the MM, make sure the MM trunk group is also listed. This will make sure the MM gets the subscriber's extension #.

Mitch


AVAYA Certified Specialist

 

[ideal]

This was happening despite the numbering format being correct. The system was still outputing a rogue zero that was not displayed on a trace but was on MST. There is now a PCN on the Avaya web site to cover this.

 

[qz01gs]

whats the PCN number

 

[btrain8]

Amazing.. if you see my threads about MM we had the same exact issue with using the *T feature. We've been on and off the phone with Avaya and the BP. We use SIP instead of QSIG and everyone was recommending going to QSIG and that wasn't the cause.

We had the latest patches put on, hairpinning turned off, codecs changed and finally Tier 4 found the solution to the problem which I will post for everyone to see. It only took several crashes, a gazillion phone conversations, reboots and late nights but finally it's working ALMOST perfectly except for some small issues.

One being Email notification.. our notifications aren't showing the date/time in them. they were at the beginning and not anymore within the email itself. Any ideas on that one?

 

[btrain8]

For the above *T issues Avaya Tier 4 had to do the following:

Resolved by enabling Send Reroute request on the hunt Group and enabling diversion by reroute on the trunk group


What's still outstanding is *T out of a mailbox over to a WAN connected site in London. Avaya states:
This is due to a limitation of MM transferring to remote subscribers.  They are investigating a workaround using secondary extensions.    The MM recognizes a transfer request from a logged-in subscriber as an attempt to transfer to a remote subscriber rather than a transfer to an extension. 

Anyone know how to fix this?