[cisco-voip] Caller-ID using MGCP and FXO ports?

[Cristobal Priego]

it works with g729
however you need a transcoder on HQ

2011/5/21 David Zhars <dzhars at gmail.com>

> UCM 8 and IOS 15 here.  (not sure of what flavor of 15).
> It works.  I seem to only get the calling number, not any name, but that
> could be a bad setup on my end.  If I plug in a regular Caller ID box, I get
> both name and number, so either the MGCP and FXO solution only provides
> calling number, or my setup is funky.
> Short answer, yes FXO and MGCP you can get caller ID.
>
> On Fri, May 13, 2011 at 12:32 PM, Haas, Neal <nhaas at co.fresno.ca.us>wrote:
>
>> If I remember correctly It will only show the extension of the port.
>>
>>
>>
>> *From:* cisco-voip-bounces at puck.nether.net [mailto:
>> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Countryman, Edward
>> *Sent:* Friday, May 13, 2011 10:25 AM
>>
>> *To:* cisco-voip at puck.nether.net
>> *Subject:* [cisco-voip] Caller-ID using MGCP and FXO ports?
>>
>>
>>
>> Does anyone know definitely if telco caller id is support on FXO ports
>> controlled by MGCP?
>>
>>
>>
>> In reading Cisco’s website it implies it is (with certain IOS) but there
>> are countless blogs indicating it does not work.
>>
>> _______________________________________________
>> cisco-voip mailing list
>>
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110521/f040893b/attachment.html>