07-25-2007 09:31 AM - edited 03-14-2019 10:45 PM
Does anyone know if there are any updates to this? The case is a known issue where an MGCP GW does not support Caller ID when T1-CAS is being used. The workaround is to configure the GW as h323. thanks
Solved! Go to Solution.
07-25-2007 10:08 AM
Caller ID is not supported on T1 CAS E&M. Nothing to do with H.323 or MGCP.
The only way to do Caller ID on T1 CAS is with T1 FGD. That is supported in
H.323, not MGCP. No plans afaik.
You can also do it in one direction only with T1 CAS FXS (send) and T1 CAS
FXO (receive) but this is typically used only for channel-bank connections
and not for PBX or PSTN connections. CCM supports only T1 CAS E&M with
MGCP, so if FXS or FXO signaling is an option in your situation, then that
too will require H.323.
07-25-2007 10:08 AM
Caller ID is not supported on T1 CAS E&M. Nothing to do with H.323 or MGCP.
The only way to do Caller ID on T1 CAS is with T1 FGD. That is supported in
H.323, not MGCP. No plans afaik.
You can also do it in one direction only with T1 CAS FXS (send) and T1 CAS
FXO (receive) but this is typically used only for channel-bank connections
and not for PBX or PSTN connections. CCM supports only T1 CAS E&M with
MGCP, so if FXS or FXO signaling is an option in your situation, then that
too will require H.323.
07-25-2007 11:13 AM
Thanks for the information
09-28-2007 02:28 PM
I configured "ring number 2" on my voice port and it works.
it is on FXO-GROUND-START signalling
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide