Written By: |
Kenny Pearl |
|---|---|
|
Manufacturer: |
Avaya |
|
Product: |
Communication Manager |
|
Version: |
Any |
|
Patch Information: |
N/A |
|
Ticket Number(s): |
Details
This article will show you the layout used when interpreting messages and IP Phone MST traces taken from a Communication Manager system.
Description
This article assumes that you have an MST trace you need to decipher or have some familiarity in running an MST trace.
Notes
The data contained within this article works on just about every release of Communication Manager and phone.
Please note that the data contained within this article does not apply to analog stations as they are not multi-line phones.
Example
Below we have an example button push from an IP phone at 172.30.110.214 to Communication Manager at 172.30.2.20.
The IP phone has bushed button number 8.
We will use this message to reference our station button map at the bottom of the article.
| 683 09:12:31.725 82 == INFO crv 0_0001 From IPAdr: 172.30.110.214 From Port:1720 To IPAdr: 172.30.2.20 To Port:61443 UID: 0x9f5c D-channel port number: 00000000 Protocol Discriminator: 08 call control Call Reference Value: 02 00 01 Origination 0001 Q.931 Message Type: 7b Information = USER-USER | Reference page(s): <> P-IV-4-92, B-V-A-124, A1-51 | 7e=oct1 ie identifier: User-to-User Information | 1e=oct2 contents length: 30 | 05=oct3 protocol discrim: ASN1 characters | 10=oct4 user information: 27 bytes | 10 01 00 10 a0 01 00 13 01 00 0a 60 86 48 01 86 f8 72 04 02 0a | 05 05 38 00 7f 08 Decode User Information: H323-UserInformation SEQUENCE [fieldcount (not encoded) = 1] h323-uu-pdu H323-UU-PDU SEQUENCE [root fieldcount (not encoded) = 1] h323-message-body CHOICE [index = 8] empty NULL [length (not encoded) = 0.0] NULL h245Tunneling BOOLEAN [length (not encoded) = 0.1] FALSE nonStandardControl SeqOfNonStandardParameter SEQUENCE OF [count = 1] NonStandardParameter SEQUENCE [fieldcount (not encoded) = 2] nonStandardIdentifier NonStandardIdentifier CHOICE [index = 0] object ObjectIdentifier OBJECT IDENTIFIER [length = 10.0] { 2 16 840 1 113778 4 2 10 } data OctetString OCTET STRING [length = 5.0] 0x0538007f08 Total PDV length = 28.0 Uplink CCMS Value 81A05:81A0501:button change: dial pad:btn num=0t8<></></> |
Dial Pad Button Mapping
| Phone Dial Pad | MST trace value |
| 1 | dial pad:btn num=0t1 |
| 2 | dial pad:btn num=0t2 |
| 3 | dial pad:btn num=0t3 |
| 4 | dial pad:btn num=0t4 |
| 5 | dial pad:btn num=0t5 |
| 6 | dial pad:btn num=0t6 |
| 7 | dial pad:btn num=0t7 |
| 8 | dial pad:btn num=0t8 |
| 9 | dial pad:btn num=0t9 |
| * | dial pad:btn num=0t10 |
| 0 | dial pad:btn num=0t11 |
| # | dial pad:btn num=0t12 |
Phone line key Button mapping
The first call appearance on any IP or digital phone will be 0t7 (just like when doing our list trace to make a call remotely). If you page to your next set of buttons the button that was in button 7's place will now be button 0t15. The MWI light is button number 0t6 and the hold, transfer, and conference buttons are 0t5, 0t4, and 0t3.
Each line key button in Communication Managers eyes will have 2 colors, red and green. Depending on the feature assignment and usage of these buttons you will see different results in an MST
| Buttons | States |
| Red or Green Lamp | Steady (light is on lit steady) |
| Red or Green Lamp | Dark (light is off) |
| ?? | Flutter (light is flashing) |
Tips
An idle phone will have the red lamp on call appearance 7 lit steady at all times
There is a lot of traffic in an MST trace for a simple station to station call, you have to know the context.
When looking at user activity with an MST always add a screen shot of the stations button layout to your ticket to make reading your trace easier.
Disclaimer: intlx Solutions Knowledge Base
The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.
Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.
Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.
Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.
Thank you for your understanding.