Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Any updates to TAC Case 48396653

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

1 ACCEPTED SOLUTION

Accepted Solutions
Green

Re: Any updates to TAC Case 48396653

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.

3 REPLIES
Green

Re: Any updates to TAC Case 48396653

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.

New Member

Re: Any updates to TAC Case 48396653

Thanks for the information

New Member

Re: Any updates to TAC Case 48396653

I configured "ring number 2" on my voice port and it works.

it is on FXO-GROUND-START signalling

119
Views
0
Helpful
3
Replies
CreatePlease to create content