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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Integration of Nec sv8100 with cucm 7.5

Hi,

I have a case here. We been trying to integrate nec sv8100 with cucm 7.0 using sip trunk. From the log I see the connection is coming in from the router 2900 but then it got drop with the error 404.

The topology is cucm-c2900-sv8100.

Anyone can help me on this?

Sent from Cisco Technical Support Android App

5 REPLIES
Hall of Fame Super Gold

Re: Integration of Nec sv8100 with cucm 7.5

First of all you don't need to go trough the router, you can have the trunk built directly to the other system.

Then, 404 means, in practice, wrong number, so check that.

New Member

Re:Integration of Nec sv8100 with cucm 7.5

Hi,

After I do some debug. I also found out that the cm is using h.323 here. So I know where is the problem now, but i have a problem with the SI where he do not want me and my team to touch the cm. The integration will be temporary till the customer's budget kicks in for expansion. Is there any brief document for this. As i need to convince the SI.

Kind Regards,

Dennis

Sent from Cisco Technical Support Android App

Hall of Fame Super Gold

Integration of Nec sv8100 with cucm 7.5

You can find material in SRND and other PBX integration documents. However, do not expect they will be specific to your own model.

New Member

Re:Integration of Nec sv8100 with cucm 7.5

Ah yes i have gone thru most of the document. Hmmm. I still stuck at the call id in nec. It seems this value is important. But i dont know where does this apply in cm. Will test further. Hope i can get it done and will document it. Also to share.

Sent from Cisco Technical Support Android App

Hall of Fame Super Gold

Integration of Nec sv8100 with cucm 7.5

Call ID field  is generated automatically for all protocols, and there is no configuration for it.

1267
Views
0
Helpful
5
Replies