|
Home > Archive > Voice over IP Cisco > December 2005 > Inbound Calling Name
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Inbound Calling Name
|
|
| Jason Burwell 2005-12-19, 5:45 pm |
| On CCM 3.3.4 can you get Inbound Calling Name when using 4ESS Protocol?
Using 6608 as a Gateway.
Thanks!
Jason
****************************************
******************************
The information transmitted is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender and delete the material from
any computer.
****************************************
******************************
| |
| Hart, Kevin 2005-12-20, 5:45 pm |
| Hi Jason,
We are running CCM 4.1 with the 6608 blades using PRI 4ESS protocol and the
Send Calling Name In Facility IE option is grayed out in the PRI Protocol
Type Specific Information screen. Based on this fact, I would assume that
inbound CID with name is not possible using this protocol. If your ISDN
vendor supports NI2 then this will probably work.
Kevin
_____
From: Jason Burwell [mailto:BurwellJ@firstcharter.com]
Sent: Monday, December 19, 2005 4:40 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Inbound Calling Name
On CCM 3.3.4 can you get Inbound Calling Name when using 4ESS Protocol?
Using 6608 as a Gateway.
Thanks!
Jason
****************************************
******************************
The information transmitted is intended only for the person or entity to
which it is
addressed and may contain confidential and/or privileged material. Any
review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon,
this information by persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and delete the
material from
any computer.
****************************************
******************************
________________________________________
_____________________________
This email has been scanned by the MessageLabs Email Security System.
________________________________________
_____________________________
This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this
message is strictly prohibited. If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any
copy or distribution. Thank you.
| |
| Ryan Ratliff 2005-12-20, 5:45 pm |
| If the protocol supports caller name in a Display IE rather than
Facility then it should work just fine. MGCP NI2 is the only
protocol type we support caller name in Facility IE though.
-Ryan
On Dec 20, 2005, at 11:14 AM, Hart, Kevin wrote:
Hi Jason,
We are running CCM 4.1 with the 6608 blades using PRI 4ESS protocol
and the Send Calling Name In Facility IE option is grayed out in the
PRI Protocol Type Specific Information screen. Based on this fact, I
would assume that inbound CID with name is not possible using this
protocol. If your ISDN vendor supports NI2 then this will probably work.
Kevin
From: Jason Burwell [mailto:BurwellJ@firstcharter.com]
Sent: Monday, December 19, 2005 4:40 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Inbound Calling Name
On CCM 3.3.4 can you get Inbound Calling Name when using 4ESS
Protocol? Using 6608 as a Gateway.
Thanks!
Jason
****************************************
******************************
The information transmitted is intended only for the person or entity
to which it is
addressed and may contain confidential and/or privileged material.
Any review,
retransmission, dissemination or other use of, or taking of any
action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited.
If you received this in error, please contact the sender and delete
the material from
any computer.
****************************************
******************************
________________________________________
_____________________________
This email has been scanned by the MessageLabs Email Security System.
________________________________________
_____________________________
This email message, including any attachments, may contain
confidential and proprietary information for the sole use of the
intended recipient. If you are not the intended recipient, you are
hereby notified that any use, copying or dissemination of this
message is strictly prohibited. If you received this message in
error, please notify Brooks Automation, Inc. immediately by reply
email or by calling Brooks US Headquarters at +1 978-262-2400. Then
delete this message from your system, without making any copy or
distribution. Thank you.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Wes Sisk 2005-12-29, 5:46 pm |
| 4ess is the only protocol CM cname feature does not work for.
cname = name delivery via facility IE.
if your carrier/pbx can send it in a DisplayIE CM will display it.
/Wes
On Dec 19, 2005, at 4:39 PM, Jason Burwell wrote:
On CCM 3.3.4 can you get Inbound Calling Name when using 4ESS
Protocol? Using 6608 as a Gateway.
Thanks!
Jason
****************************************
******************************
The information transmitted is intended only for the person or entity
to which it is
addressed and may contain confidential and/or privileged material.
Any review,
retransmission, dissemination or other use of, or taking of any
action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited.
If you received this in error, please contact the sender and delete
the material from
any computer.
****************************************
******************************
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|