Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-08-2010, 11:59 PM
wnie wnie is offline
Member
.
 
Join Date: Feb 2010
Posts: 7
wnie has 10 reputation points
Question Questions about CDR and Bridged Call Appearance

Dear mates,

I got three questions about CDR and Bridged Call Appearance,as below:

1. While using Bridged Call Appearance feature, CDR can just record Primary Phone's information. Even Bridged Appearance Phone receive inbound call and make outbound call, CDR also record data as Primary Phone Number?
2. Whether Bridged Appearance can transfer the call to other phone?
3. On CM, Coverage-Path to other Vendor's Voice Mail System, but it doesn't work, I think the Voice Mail may not recognize AVAYA's busy/no-answer signal?


Hope you can help to provide some suggestions.
Thanks very much in advance.

Best Regards!
Reply With Quote
  #2  
Old 04-12-2010, 01:28 AM
rsadarangani rsadarangani is offline
Member
.
 
Join Date: Mar 2010
Posts: 7
rsadarangani has 10 reputation points
Default

Hi Wnie

Please find the my suggestion to your questions:

1. While using Bridged Call Appearance feature, CDR can just record Primary Phone's information. Even Bridged Appearance Phone receive inbound call and make outbound call, CDR also record data as Primary Phone Number?
As the Bridged Call Appearance is the key assigned on the extn for the primary phone, it has all the same features to be used on primary phone
so whenever you dial the number using that Bridged appearance key it will log the calls to primay extn on CDR.
2. Whether Bridged Appearance can transfer the call to other phone?

Yes you can transfer the call to other phone if you have enough call appearance assigned ( required min. of two keys for the primary extn as bridged appearance keys) on the extn.
3. On CM, Coverage-Path to other Vendor's Voice Mail System, but it doesn't work, I think the Voice Mail may not recognize AVAYA's busy/no-answer signal?

For this you need to read the third party vendor document and check what link you are creating between Avaya CM and 3rd party VM.

Regards
Ravi
Reply With Quote
  #3  
Old 04-12-2010, 08:09 AM
pappaka pappaka is offline
Hot Shot
.
 
Join Date: Mar 2010
Posts: 11
pappaka has 10 reputation points
Default Reply

If the issue with coverage path to 3rd party voice mail exists with recommended configurations, I would suggest that you either create an online Service Request at http://support.avaya.com/ >> "Create Service Request", or call into the support center to ask this technical question.
Reply With Quote
  #4  
Old 04-18-2010, 07:38 PM
wnie wnie is offline
Member
.
 
Join Date: Feb 2010
Posts: 7
wnie has 10 reputation points
Default

Thanks very much for all your kindly help.
Reply With Quote
  #5  
Old 04-19-2010, 07:32 PM
wnie wnie is offline
Member
.
 
Join Date: Feb 2010
Posts: 7
wnie has 10 reputation points
Question Something more need be confirmed, Thanks very much.

I still have some questions that need be clarified with you.

1. While using Bridged Call Appearance feature, CDR can just record Primary Phone's information. Even Bridged Appearance Phone receive inbound call and make outbound call, CDR also record data as Primary Phone Number?
As the Bridged Call Appearance is the key assigned on the extn for the primary phone, it has all the same features to be used on primary phone
so whenever you dial the number using that Bridged appearance key it will log the calls to primay extn on CDR.


// As I understand for your explanation, both inbound call and outbound call, which are placed on Primary Phone or Bridged Appearance Phone, will always be registered as Primary Phone number in CDR.
// And there is no related parameter for changing it, am I right?
// If It is, is there any official document for this character? and where may I get it?

2. Whether Bridged Appearance can transfer the call to other phone?
Yes you can transfer the call to other phone if you have enough call appearance assigned ( required min. of two keys for the primary extn as bridged appearance keys) on the extn.


// I found one description in CM4 documentation:
// So, the transfer feature can be used on Primary Phone and Bridged Appearance Phone.
// But it was failed without any failed code while we made test.

11:03:10 ring station 402 cid 0x135
11:03:14 active station 116 cid 0x135
11:03:16 transfer station 194 cid 0x135
11:05:53 idle trunk-group 1 member 13 cid 0x135
11:06:03 idle station 116 cid 0x137



// Both Primary Phone and Bridged Appearance Phone are with at least two "call-appr" buttons.
// Check the station parameter based on the Insite Document ID: KB01045096

Display station xxxx

Page 2 of 5
Restrict Last Appearance? y ---- Whether this should be n

Page 3 of 5
Conf/Trans on Primary Appearance? n ---- Whether this should be y

3. On CM, Coverage-Path to other Vendor's Voice Mail System, but it doesn't work, I think the Voice Mail may not recognize AVAYA's busy/no-answer signal?
For this you need to read the third party vendor document and check what link you are creating between Avaya CM and 3rd party VM.


As I heard there is one parameter in CM system used to control the sending code to Voice Mail System, such as code for busy signal or no-reply signal.
So that, Voice Mail system can choose the matched code to record voice.
What's your opinion on it?

Thanks again for your great help.
Hope you can provide the suggestions on it with your convenience.

Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:08 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.