Glad to hear you had a workaround.
I would suggest re-queing your TAC case, perhaps you got a outsourced or less
experienced engineer at Cisco. Their support has varied depending on which
city/group you get. Some have more experience then others.
While your 2600 from 2001 timeframe it should work, you can't run any of 12.4T
images over the last 3 years without maxing the DRAM/Flash.
I've got 1200+ Forced Authorization Codes with 4.1(3)SR1 using
2811ISRs/VWIC2-1MFT-T1s running 12.4T with both MGCP and H323 gateways across
20 sites with no issues. Could be the old 2600s IOS as you mentioned.
________________________________
From: [EMAIL PROTECTED] on behalf of JR Richardson
Sent: Wed 2/21/2007 8:01 PM
To: asterisk-users@lists.digium.com
Subject: [asterisk-users] Asterisk to Cisco's Rescue...again...AuthenticateLD
Calls
Hi All,
Just wanted to share a story:
We turned up a new customer yesterday evening, typical situation, Cisco 2600
Router with T1 PRI card pointed to the customer's analog PBX with 2 data T1's
linked back to our network. The router PRI was configured as a gateway on our
CCM 4, like we've done numerous times in the past. The customer needed LD
Authorization codes enabled, got the list 400+, and configured them in the CCM,
no problem. We started passing calls, local was fine but the LD would not
work, turned the LD codes off and LD would work. After engaging Cisco TAC, was
informed that LD coded do not work with this type of gateway device.
After strapping on my Asterisk-Orange Super-Engineer Cape and Goggles, I told
my Cisco Guy to prepend all the LD traffic with a 3 digit code and send it to
one of my Cluster Asterisk Servers. I put in a pattern for matching just this
customers LD traffic as so:
exten => _5551NXXNXXXXXX,1,Answer
exten => _5551NXXNXXXXXX,2,Set(CDR(userfield)=Company LD)
exten => _5551NXXNXXXXXX,3,Authenticate(/etc/asterisk/companyld.codes|a)
exten => _5551NXXNXXXXXX,4,Goto(ccmtrunkld|${EXTEN:3}|1)
;Answer because the authenticate cmd sends audio back to the caller
;set the CDR userfield to the company name
;Authenticate with file where the LD codes are stored, 'a' option puts the LD
code in the CDR accountcode field
;strip the 555 off and pass the LD call outbound
So now all the LD traffic from this customer can be authenticated from the
codes in the file companyld.codes, the CDR is updated properly for parsing the
LD and generates a nice monthly report for tracking who is using LD for this
customer.
I guess I'm feeling grateful that the Cisco Gateway is passing calls in the
first place, but it would have been nice for the Cisco CM and the Cisco Gateway
to play nice together.
The real hero here is Asterisk, Digium, and the Community that supports it!
Thank you All
JR
JR Richardson
Engineering for the Masses
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you._______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
