Dialogic
Search
Worldwide
中文 (CHINA)
CANADA English [EN]
CANADA Français [FR]
D/A/CH
NORTHERN EUROPE
日本 (JAPAN)
Contact
DEN
PRODUCTS
SOLUTIONS
TECHNOLOGIES
PURCHASE
PARTNERS
SERVICE CENTER
COMPANY
Dialogic Service Center
Service Contracts
Dialogic
®
Pro™ Contracts
Dialogic
®
Pro™ Summary
Value Per Unit Plan
Standard Per Unit Plan
Premium Per Unit Plan
Standard Service Agreement
Premium Service Agreement
Carrier Pack
Contracts by Product
Contracts by Customer Type
Contracts by Requirement
Technical Helpweb
Helpweb Menu
Helpweb Menu
Dialogic API information
DM3 & JCT products
Host Media Processing (HMP)
Brooktrout
®
Fax
IP Media Server
IMG Gateways
CSP Platforms
MSP Platforms
DMG-series Media Gateways
Signaling & SS7 Components
Multimedia Platform for ATCA
®
Diva
®
Media Boards
Diva
®
SDK
Vision™ Servers & Gateways
NaturalAccess™ products
Diva
®
Client
Eiconcards (X.25)
Other Dialogic products
Downloads
Software Download wizard
Software Download listing
Manuals & Documentation
Document Finder
Contact Support
Select Support region
Americas Support
AsiaPac Support
EMEA Support
Online Service Request
Developer Forums
Developer Forums Menu
Dialogic
®
Global Call Forum
Dialogic
®
Diva
®
SDK Forum
SS7 and Sigtran Signaling Forum
Training
Training Menu
On-line training courses
Share
Home
Service Center
Technical Helpweb
Dialogic® DM3 & JCT Media Boards
Technical Helpweb
Dialogic® DM3 and JCT Media Boards
Incorrect Call ID on Avaya Integration for D/82JCT-U
Problem Description:
On Avaya if the extension number is not put into the name field for the subscribers, the D/82 will not properly detect call id for forwarded calls. If a number other than the extension is put into the name field of the calling party that number is picked up as part of the called/calling information.
Solution Summary:
Follow a format for setting up subscriber extensions that may be forwarded to the D/82JCT-U Avaya integration where the extension number is in the first 15 characters of the name field for each subscriber.
Technical Discussion:
The called and calling information on the Avaya integration is determined by an internal parser in the D/82JCT-U firmware. Therefore, if the display does not provide the information or the information is not accurate, then the called and calling party information will not be accurate. Example of not having the extension in the name field:
If the name field for extension 123 shows "User Name" and a call is made to 234 which is forwarded to the D/82JCT-U port then the display on the D/82JCT-U port will be [User Name calling 234 fwd]. That display will produce the following when d42_gtcallid() is used to retrieve the called and calling party information: _234.
Example of having extra numbers in the name field:
If the name field for extension 123 shows "123 User Number 7" and a call is made to 234 which is forwarded to the D/82JCT-U port then the display on the D/82JCT-U port will be [123 User Number 7 calling 234 fwd]. That display will produce the following when d42_gtcallid() is used to retrieve the called and calling party information: 123_7.
Example of a correct name field:
If the name field for extension 124 shows "123 User Name" and a call is made to 234 which is forwarded to the D/82JCT-U port then the display on the D/82JCT-U port will be [123 User Name calling 234 fwd]. That display will produce the following when d42_gtcallid() is used to retrieve the called and calling party information: 234_123.
NOTE: The application must make a slight adjustment when handling direct calls. The called and calling party for direct calls is going to be populated with the calling party. For example if extension 123 makes a call to the D/82 port d42_gtcallid() will provide the following as called and calling party information: 123_123.
Product List:
D/82JCT-U
D/82JCT-U Universal
D/42JCT-U
Glossary of Acronyms/Terms:
Subscriber – extensions on a phone system that will be either calling the PBX integration board directly or calls will be forwarded from that extension.
Related Documentation:
N/A
First Published:
03/17/2004
Last Updated:
03/17/2004
Attachments
N/A
Feedback
Please rate the usefulness of this page:
0 - not useful at all
1 - potentially useful
2 - quite useful
3 - very useful
4 - exactly the information I needed
Please enter a comment about this page: