|
Home > Archive > Voice over IP Cisco > August 2005 > FW: fxo mgcp caller-id
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 |
FW: fxo mgcp caller-id
|
|
| Greg McAllister 2005-08-03, 5:45 pm |
|
_____
From: Greg McAllister [mailto:gmcallis@mtco.com]
Sent: Wednesday, August 03, 2005 5:01 PM
To: 'cisco-voip@puck.nether.net'
Subject: fxo mgcp caller-id
Greetings.
What's the real story ?
Is it possible to display caller-id received through VIC2-FXO ports in an
MGCP (2801) gateway on cisco phones? I'm reading some disturbing information
related to FXO-received CID and MGCP not being compatible, and I cannot
believe that it can't be done since the router IOS gateway is clearly
showing the CID in the "show" commands.
Thanks, Greg.
| |
| Boda György 2005-08-04, 5:45 pm |
| FXO and T1-CAS on MGCP GWs cannot send ANI (CCM 4.1).
-----Original Message-----
From: Ryan Ratliff [mailto:rratliff@cisco.com] =
Sent: 2005. augusztus 4. 15:18
To: gregmcallister@mchsi.com
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FW: fxo mgcp caller-id
This is a limitation of the MGCP protocol as it has no facility to pass =
caller ID information except during initial call setup. Since an =
analog FXO port receives calling party information after the first ring =
(or two) it just doesn't work. To get FXO caller id you have to use =
H.323.
-Ryan
On Aug 3, 2005, at 6:02 PM, Greg McAllister wrote:
=A0
=A0
From: Greg McAllister [mailto:gmcallis@mtco.com]
Sent: Wednesday, August 03, 2005 5:01 PM
To: 'cisco-voip@puck.nether.net'
Subject: fxo mgcp caller-id
=A0
Greetings.
What's the real story ?
Is it possible to display caller-id received through VIC2-FXO ports in =
an MGCP (2801) gateway on cisco phones? I'm reading some disturbing =
information related to FXO-received CID and MGCP not being compatible, =
and I cannot believe that it can't be done since the router IOS gateway =
is clearly showing the CID in the "show" commands.
Thanks, Greg.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Ryan Ratliff 2005-08-05, 2:45 am |
| This is a limitation of the MGCP protocol as it has no facility to pass =
caller ID information except during initial call setup. Since an =
analog FXO port receives calling party information after the first ring =
(or two) it just doesn't work. To get FXO caller id you have to use =
H.323.
-Ryan
On Aug 3, 2005, at 6:02 PM, Greg McAllister wrote:
=A0
=A0
From: Greg McAllister [mailto:gmcallis@mtco.com]
Sent: Wednesday, August 03, 2005 5:01 PM
To: 'cisco-voip@puck.nether.net'
Subject: fxo mgcp caller-id
=A0
Greetings.
What=92s the real story ?
Is it possible to display caller-id received through VIC2-FXO ports in =
an MGCP (2801) gateway on cisco phones? I=92m reading some disturbing =
information related to FXO-received CID and MGCP not being compatible, =
and I cannot believe that it can=92t be done since the router IOS gateway =
is clearly showing the CID in the =93show=94 commands.
Thanks, Greg.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|