[cisco-voip] Caller ID

[Wes Sisk]

Yes, someone wrote a TCL script for this also, though I'm not sure  
why when you get 'e&m-fgd' when you define the ds0-group
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1834/ 
products_feature_guide09186a00800801ee.html

I have heard of some folks using a delimiter other than *, like #  
( #ani#dnis#) and for that the TCL script would be more flexible.

/Wes

On Feb 15, 2006, at 11:05 AM, Philip Walenta wrote:

FGB does not provide ANI, but works with MGCP.

FGD provides ANI, but only works with H.323.

I've seen TCL scripts used to capture this info and forward it  
appropriately.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip- 
bounces at puck.nether.net] On Behalf Of Voll, Scott
Sent: Wednesday, February 15, 2006 9:30 AM
To: Wes Sisk
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Caller ID

So if I understand what your saying is that with FGB and MGCP it  
works and with FGD and H323 I can make it work, Yes?







From: Wes Sisk



FeatureGroupB is vanilla wink start t1-cas.  CM supports FGB via MGCP

FeatureGroupD includes ANI, but CCM does not support FGD via MGCP.   
have to use h323 if  you want FGB.  DNIS just gets a special format  
which is *ANI*DNIS* which fails to match your route patterns in CM.   
I've seen several attempts to use translation patterns to force  
matches, but none successful.



/Wes



On Feb 13, 2006, at 6:43 PM, Philip Walenta wrote:



T1 CAS supports ANI via feature group B or D.  I know it's one of  
those two.  Only supported on a limited set of devices.



From: Jonathan Charles


BRI uses the same signaling as a PRI, so it works there

FXOs work... it will come in between the first and second ring (so if  
they pickup before the 2nd ring, no CID).

A T1 CAS is another issue... while you can see digits in debugs, I  
have never seen CID info... I would presume you can though.



Jonathan

On 2/13/06, Voll, Scott  wrote:

Can anyone tell me on what interfaces CM 4.1 can accept and display  
Caller ID.

  I know PRI's work.  What about FXO, CAS, BRI, etc.



Thank

  Scott



-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060215/9fbe0fb6/attachment-0001.html