[c-nsp] Odd MGCP issue with Caller-id

[Matlock, Kenneth L]

Just as a follow-up, and to archive this resolution.

I added 'cptone GB' to the 'voice-port 0/2/0' interface and it
immediately started working. The fax machine behind the port answered,
and all is well. That has a 20 character limit, but at least it works
short-term.

Tonight after the clinic closes I'll put the 12.4(3h) code we're running
on another clinic's 2851, and we should be good to go!

It looks like the check was enforced starting at 12.4(20)T and 12.4(21),
and I'm told the bug ID was CSCsj70344 (although it talks about calling
number, I assume they put in the checks at that point).

It'd be nice to have a command-line option to turn off the check
entirely, but for now at least there's a fix. 
 
Thanks to Oliver Boehmer for pointing me in the right direction!

Ken Matlock
Network Analyst
(303) 467-4671
matlockk at exempla.org


________________________________

From: cisco-nsp-bounces at puck.nether.net on behalf of Matlock, Kenneth L
Sent: Thu 9/4/2008 10:39 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Odd MGCP issue with Caller-id



We have a Call Manager 4.1 setup, and are using a few 2851's with FXS
cards (VIC-4FXS/DID=) as gateways using MGCP for Fax lines.



Everything is (and has) been working fine, but we have been tracing down
a problem where *some* destinations could not call these extensions
(there wasn't a rhyme or reason we could see at first).



What we finally found, was that is was based off the length of the
*calling* name. If it was 15 characters or less in call manager, it
would work, but 16+ would not (they'd get a reorder tone).



The relevant debug logs are as follows:



Sep  4 09:46:38 MDT:
//-1/7EF7044C8022/MGCP|aaln/S0/SU2/0|-1|-1/<VOICE>/gen_caller_id(9324):[
lvl=1]mode == VALIDATE cid =<09/04/09/46,24671,Ken Matlock Test Test
Test>

Sep  4 09:46:38 MDT:
//-1/xxxxxxxxxxxx/MGCP/mgcp_parse_cid_str(5889):[lvl=2]time=<09/04/09/46
> num=<24671> name=<Ken Matlock Test Test Test>

Sep  4 09:46:38 MDT:
//-1/7EF7044C8022/MGCP|aaln/S0/SU2/0|-1|-1/<VOICE>/gen_caller_id(9337):[
lvl=0]-- Country code = US

Sep  4 09:46:38 MDT:
//-1/7EF7044C8022/MGCP|aaln/S0/SU2/0|-1|-1/<VOICE>/gen_caller_id(9362):[
lvl=1]-- Caller Id type = 1

Sep  4 09:46:38 MDT:
//-1/7EF7044C8022/MGCP|aaln/S0/SU2/0|-1|-1/<VOICE>/gen_caller_id(9424):[
lvl=0]-- returns code = 54

Sep  4 09:46:38 MDT:
//-1/7EF7044C8022/MGCP|aaln/S0/SU2/0|-1|-1/<VOICE>/process_start_signal(
4062):[lvl=2]process_start_signal(): FAIL with rc: 54, need to reject
the whole list



And



Sep  4 09:46:38 MDT: MGCP Packet sent to 172.18.164.136:2427---> 510
100502 unsupported caller id length <---



I've done numerous searches on those errors, and checked the bug toolkit
for both IOS version we've tried (12.4(20)T and 12.4(21) ) and no luck.



Tried the 'caller-id block' on the port (but since it's not incoming on
the FXS port I didn't think it'd help anyway).



While we CAN go into Callmanager and shorten all the stations with 16+
character display names, I'd hate to have to go to that trouble if I can
help it. Is there a way to increase that limit, or is that a hard-set in
either the FXS cards, or MGCP?



Ken Matlock
Network Analyst
(303) 467-4671
matlockk at exempla.org



_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/