cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4663
Views
22
Helpful
20
Replies
joshhaleaos
Beginner

MGCP Caller ID FXO 8.6

Has anyone got this to work in an 8.6 environment?  It seems to work sometimes and then it stops.  The only way I can get it to start working again is by rebooting the router.  The client is running 8.6 with the 2900 series routers (latest IOS 15.2.T1).  I've got the Enable Caller-ID checked in the FXO ports, caller-id enabled on the voice ports and the MGCP res package installed.

CUCM - 8.6.1a

2901 - 15.2.T1

7940 Phones

1 ACCEPTED SOLUTION

Accepted Solutions
paolo bevilacqua
Hall of Fame Master

Why not taking the easy way and insist on an inferior solution ?

With H.323 or SIP, you would have everything working perfectly by now, and many more features and manageability.

View solution in original post

20 REPLIES 20
Payal Bhaduri
Cisco Employee

Hi,

Can you try putting in the following command?

(config)#mgcp persistent offhook

Hello,

Any success with this problem. I have the same issue.

Thanks

Hello!

Can you please try under the voice-ports the following command:

voice-port x/x/x

timing guard-out 1000

Then do a shut - no shut on the voice ports

Please make some test calls and let us know.

Jorge

-- Jorge Armijo Please remember to rate helpful responses and identify helpful or correct answers.

It is true. However, line:

timing guard-out 1000

disappears after a while and the caller ID issue appears again.

Is there anyway to resolve it permanently?

Hi Christapor,

 

please try these commands in addition to timing guard-out and mgcp persistent offhook

caller-id enable

caller-id alerting line-reversal

caller-id alerting dsp-pre-allocate

 

regds,

aman

Hi Aman,

 

could this be an issue with the IOS? may be 15.4 ?

 

I too faced this issue but then i moved to H323, can you help?

 

thanks.

Hi,

 

you mean to say issue got resolved when u are using H.323 .

 

What is the existing IOS version?

 

regs,

aman

i did had to upgrade the IOS to 15.4.

You mean to say caller-ID problem got resolved by upgrading the IOS to 15.4.

 

Lastly , CallerID is working OK with H.323 and MGCP on 15.4.Please confirm.

 

regds,

aman

Caller id issue got resolved moving to H323....

 

i was asking you could IOS issue be the cause for MGCP?

 

i have upgraded the IOS to 15.4  but have not tested MGCP but H323 works fine.

 

Thanks.

suggestions are welcome [+5]

 

what was earlier version from which u migrated to 15.4 and problem got resolved?

 

regds,

aman

we were on 15.1 first version  dont remember though.

 

if you have a test environment can you check with MGCP?

 

thanks.

paolo bevilacqua
Hall of Fame Master

Why not taking the easy way and insist on an inferior solution ?

With H.323 or SIP, you would have everything working perfectly by now, and many more features and manageability.

View solution in original post

Paolo, I like your thinking, I myself have been staying away from MGCP for few years, and only do it when I am forced. I get the benefit from centralized dial plan management, but as you point out too many culprits to deal with.

Chris

Content for Community-Ad

Spotlight Awards 2021