cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5406
Views
10
Helpful
8
Replies
Beginner

CUCM8 caller id issue with FXO/FXS using MGCP

Hi,

I thought caller id support was included using MGCP with FXS/FXO but I am still having issues.

here is my setup

CUCM8

2621XM with VIC-2FXS and VIC-2FXO-M1 and 12.4-25D IOS

using IP phone as well as analog phone connected to FXS port above.

First issue is with FXO using MGCP. I do get callerid on router but does not pass that to CUCM while running MGCP. It works fine if I use H323.

I thought CUCM8 resolved this issue with MGCP but I guess it still does not work with older VIC cards. I prefer to use MGCP. Let me know if you can suggest something.

Second issue is callerid with FXS port. I don't get callerid if running this using MGCP but i get caller id fine on IP phone (provided I am running H323 on FXO port) for incoming call from PSTN. I prefer to use MGCP and that way CUCM handle all call routing.

Let me know if only solution is to upgrade the VIC card here.

thanks,

Sam

8 REPLIES 8
Participant

Re: CUCM8 caller id issue with FXO/FXS using MGCP

Sam,

     Your right MGCP FXO Caller ID was one of the headline feature but if you check the admin guides at 8.x it still isn't supported. MGCP controlled FXS is listed as basic calls only.

          CuCM 8.0(1)

               http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_0_1/ccmsys/a08gw.html#wp1165631

          CuCM 8.5(1)

               http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_5_1/ccmsys/a08gw.html#wp1165631

     I suspect that upgrading your card will not change the function.

Hope this helps,

Craig

(PLEASE RATE HELPFUL POSTS)

Beginner

Re: CUCM8 caller id issue with FXO/FXS using MGCP

thanks Craig!

Does that mean caller id is still not working using MGCP with FXO regardless of hardware?

Highlighted
Enthusiast

Re: CUCM8 caller id issue with FXO/FXS using MGCP

I had the same issue. The following commands resolved this for me.

voice-port 0/2/0
  timing guard-out 1000
  shut
  no shut

mgcp persistent offhook

Rising star

Re: CUCM8 caller id issue with FXO/FXS using MGCP

Thank you very much! Your solution solved my problem with FXO+MGCP callerid

Beginner

CUCM8 caller id issue with FXO/FXS using MGCP

This doesn't work for me. I do see call come in with caller-id, but looks like not being sent to cucm.

Any help is appreciated.

Thanks

Andrew

ios is 15.2

cucm is 8.5.1

ccm-manager mgcp

no ccm-manager fax protocol cisco

ccm-manager music-on-hold

ccm-manager config server 1.0.0.85

ccm-manager config

!

mgcp

mgcp call-agent cucm85 2427 service-type mgcp version 0.1

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

mgcp default-package mt-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

!

mgcp profile default

ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 1.0.0.85
ccm-manager config
!
mgcp
mgcp call-agent cucm85 2427 service-type mgcp version 0.1
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
mgcp default-package mt-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
!
mgcp profile default

voice-port 0/1/1

timing guard-out 1000

description

caller-id enable

.

.

.

*Jan 24 15:16:28.747: //176/392DB3448177/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=8183644000(TON=Unknown, NPI=Unknown, Screening=Not S
creened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown))
*Jan 24 15:16:28.751: [0/1/1] htsp_dsm_close_done
*Jan 24 15:16:28.751: htsp_process_event: [0/1/1, FXOLS_WAIT_SETUP_ACK, E_HTSP_S
ETUP_ACK]
*Jan 24 15:16:28.751: fxols_wait_setup_ack:
*Jan 24 15:16:28.751: [0/1/1] set signal state = 0xC timestamp = 0fxols_check_au
to_call
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/cc_process_call_setup_ind:
   Event=0x899BDCE8
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 176 with tag 11 to app "MGCPAPP"
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/ccCallSetContext:
   Context=0x8A655B08
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/ccCallSetupAck:
   Call Id=176
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/cc_api_set_transfer_info:
   Transfer Number=, Transfer Reason=0x0
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/ccCallConnect:
   Progress Indication=NULL(0), Data Bitmask=0x0
*Jan 24 15:16:28.751: //176/392DB3448177/CCAPI/ccCallConnect:
   Call Entry(Connected=TRUE, Responsed=TRUE)
*Jan 24 15:16:28.751: htsp_process_event: [0/1/1, FXOLS_PROCEEDING, E_HTSP_SETUP
_ACK]
*Jan 24 15:16:28.755: htsp_process_event: [0/1/1, FXOLS_PROCEEDING, E_HTSP_CONNE
CT]fxols_offhook_connect
*Jan 24 15:16:28.755: htsp_timer_stop
*Jan 24 15:16:29.023: htsp_process_event: [0/1/1, FXOLS_CONNECT, E_DSP_SIG_0110]
fxols_rvs_battery
*Jan 24 15:16:29.023: htsp_timer_stop2
*Jan 24 15:16:29.023: htsp_timer_stop2
*Jan 24 15:16:31.783: //176/392DB3448177/CCAPI/ccCallModify:
   Nominator=0x1, Params=0x877C31A8, Call Id=176
*Jan 24 15:16:31.783: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x89FB4EE4, Interface Type=9, Destination=0.0.0.0, Mode=0x9,
   Call Params(Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screeni
ng=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=, FinalDestinationFlag=FALSE, Outgoing Dial-peer=0, Call
Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Appl
ication Call Id=)

sh voice port 0/1/1

Foreign Exchange Office 0/1/1 Slot is 0, Sub-unit is 1, Port is 1
Type of VoicePort is FXO
Operation State is DORMANT
Administrative State is UP
The Last Interface Down Failure Cause is Administrative Shutdown
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to 0 dB
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 128 ms
Echo Cancel worst case ERL is set to 6 dB
Playout-delay Mode is set to adaptive
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 1000 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is normal
Connection Number is not set
Initial Time Out is set to 15 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Power Denial Disconnect Time Out is set to 1000 ms
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 30 s
Companding Type is u-law
Region Tone is set for US

Analog Info Follows:
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Station name None, Station number None

Caller ID Info Follows:
Standard BELLCORE
Caller ID is received after 1 ring(s)
Translation profile (Incoming):
Translation profile (Outgoing):
lpcor (Incoming):
lpcor (Outgoing):

Voice card specific Info Follows:
Signal Type is loopStart
Battery-Reversal is enabled
Number Of Rings is set to 1
Supervisory Disconnect is signal
Answer Supervision is inactive
Hook Status is On Hook
Ring Detect Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Dial Out Type is dtmf
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Percent Break of Pulse is 60 percent
GuardOut timer is 1000 ms
Minimum ring duration timer is 125 ms
Hookflash-in Timing is set to 600 ms
Hookflash-out Timing is set to 400 ms
Supervisory Disconnect Timing (loopStart only) is set to 350 ms
OPX Ring Wait Timing is set to 6000 ms
Secondary dialtone is disabled

Advocate

CUCM8 caller id issue with FXO/FXS using MGCP

Hi,

Can you try changing the input gain of your FXO port
just as a test


!
voice-port 0/1/1
input gain -6
caller-id alerting dsp-pre-alloc
!

If it still does not work put the gain back to 0


!
voice-port 0/1/1
input gain 0
!


Worth a try


Regards
Alex

Regards, Alex. Please rate useful posts.
Beginner

Re: CUCM8 caller id issue with FXO/FXS using MGCP

Tried input gain -6, but still no caller-id is sent from mgcp gateway.

Hall of Fame Master

Re: CUCM8 caller id issue with FXO/FXS using MGCP

First issue is with FXO using MGCP. I do get callerid on router but does not pass that to CUCM while running MGCP. It works fine if I use H323.

I thought CUCM8 resolved this issue with MGCP but I guess it still does not work with older VIC cards. I prefer to use MGCP. Let me know if you can suggest something.

It is not a matter of preferences. H.323 is a better choice under all aspects, as you have found yourself.

Second issue is callerid with FXS port. I don't get callerid if running this using MGCP but i get caller id fine on IP phone (provided I am running H323 on FXO port) for incoming call from PSTN. I prefer to use MGCP and that way CUCM handle all call routing.

Again, you are using the wrong protocol. For FXS ports you should use SCCP instead.

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards