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

CLI on CCM

Just a quick one, could someone point me in the right direction on how to configure the gateway / CCM, so that when a call is made, the called party can see the number and extension of the calling party. AT the moment the called party just receives 0115557000, instead of 0115557013 for example. So when a call is missed by the called party, they can simply redial the missed call instead of getting to the switchboard.

Thanks in advance

2 REPLIES
Cisco Employee

Re: CLI on CCM

CLI = Command Line Interface

CLID = Calling Line ID

sounds to me that your telco might be sending the main number for your calls.

you can set it at the phone, under external phone number mask and check the checkbox under the route pattern. under the route pattern, and under the route group

if you set it and still no avail get a debug isdn q931, if you're sending the right info, call telco, they're overriding it

HTH

javalenc

if this helps, please rate

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Community Member

Re: CLI on CCM

Ok, I'm sure that'll work, will post the results as I can only make this change after hour (changes to sip trunks will reset them).

I'm also getting some errors with these sip trunks to the gateway:

*Jun 23 08:47:39.326: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 23 10:38:12.597: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 23 10:52:23.069: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 07:29:29.324: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:33:21.732: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:33:27.768: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:33:33.832: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:33:57.016: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:34:07.084: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 09:34:16.156: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 24 10:21:26.363: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 25 08:36:13.342: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 25 10:16:15.645: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 25 14:37:42.548: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 26 05:58:29.125: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 26 08:19:17.216: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 27 09:08:58.198: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 27 09:26:25.586: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 27 12:04:58.145: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 07:41:36.984: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 09:12:33.856: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 09:41:46.676: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 09:46:12.112: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 10:06:41.120: %SIP-3-UNSUPPORTED: Unsupported ptime value

*Jun 30 12:25:21.079: %SIP-3-UNSUPPORTED: Unsupported ptime value

Any ideas what this is and how to resolve it as it seems to drop all active calls when this occurs.

Also when dialling out, and say for example you reach a number that is busy, like an analog phone on the telco's network, instead of receiving a busy tone signal it rings 2/3 times and then cuts off, is there something I could do to rectify this.

Thanks for your help

310
Views
5
Helpful
2
Replies
CreatePlease to create content