cups / mpe

Unanswered Question
Mar 29th, 2009

have a conferencing server setup for cups but on client it says the conferencing server is not available.

what has to be done on mpe for this to work?

There are no creds required for this so what exactly is this doing?

I've tried name/ip and both ip's on mpe server and no go.

Help?

thx.

paul.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
htluo Sun, 03/29/2009 - 18:56

Hi Paul,

Please be more specific, so we can understand the problem.

"have a conferencing server setup for cups"

- How was it set up? Where did you set it up? (on CUPS Admin or MPE Admin?)

"but on client it says the conferencing server is not available"

- On CUPS Admin, did you create a conferencing profile?

- Did you assign users to this profile?

- On CUPC > File > Preference > Accounts, did you set up the user credential?

For more tech tips, please see: http://htluo.blogspot.com/

Thanks!

Michael

pvarenholt Mon, 03/30/2009 - 04:15

Have mpe - vt setup on server.

Created conf server

created conf profile and have users associated.

did not have the cupc user account done but it is now done but still not working.

I'm looking in the CUPC->Help->Show Server Health.

I've tried both ip addresses of mpe server and tried names as well and no luck.

htluo Mon, 03/30/2009 - 20:42

From the last logon, we can see:

MeetingPlace.Primary.Address = bsifrempew1.bulletproofsi.com

From the CUPC computer, bring up a web browser (Internet Explorer). Type "http://bsifrempew1.bulletproofsi.com". Can you log into meetingplace?

Thanks!

Michael

pvarenholt Tue, 03/31/2009 - 04:34

yep.

this has to be something simple.

i've tried ip addresses and have tried both IP's and names.

i'm assuming the proper one to use is the web address correct?

I can also ping this from the cups box.

htluo Tue, 03/31/2009 - 06:26

You can use either IP address or DNS name if HTTP is allowed on MPE.

Here's what I found in the logs:

1) When you use DNS name for MPE, it CUPC doesn't attempt the connection at all. This might be caused by DNS issue. (DNS might be more complicated than we had thought, see http://htluo.blogspot.com/2009/01/name-resolution-for-cisco-voice.html)

2) Could you tell me what are the following IP addresses?

172.19.174.23

172.19.174.24

172.19.170.23

172.19.170.24

172.19.180.23

I saw that during login, CUPC tried the above address (as logon server) before it can finally connect to CUPS (172.19.180.23), which really confused me. Did somebody manually enter those IP addresses on the logon window?

Thanks!

Michael

pvarenholt Tue, 03/31/2009 - 06:54

The 174 subnet is the data and this may have been done in error.

the 170 subnet is voice as is the 180.

170.23 is mpe web NIC

170.24 is mpe voice NIC

180.23 is CUPS

As I said I tried several different IP's and must have done the 174 subnet by accident (not paying attention) - sorry.

So are you saying to change everything including the CUPC login to ip as well as the conf server?

I'll do that and attach logs again.

pvarenholt Tue, 03/31/2009 - 07:00

logged in via ip and had conf server setup as ip address.

logs attached.

this is more difficult than i thought.

thought this was something simple that i've forgotten.

In preferences / accounts in cupc - the account settings should be same as i would use to login to web page via mpe correct?

htluo Tue, 03/31/2009 - 10:20

It looks like CUPC attempted the MPE but didn't get response:

2009-03-31 10:55:16,371 [0x00001710] DEBUG LCConnection - WEB_COLLAB startConnection(): 172.19.170.23:80(http)

2009-03-31 10:55:16,371 [0x00001710] DEBUG LCConnection - WEB_COLLAB setState(): [IDLE] --> [CONNECTING_PRIMARY]

Would you be able to do a sniffer on CUPC machine and see if the MPE (172.19.170.23) every responded?

Thanks!

Michael

htluo Tue, 03/31/2009 - 11:56

I couldn't find any packets in the capture with IP address 172.19.170.23.

I think you'd better open a TAC case for that. Never seen this before.

Michael

keithknowles Fri, 09/11/2009 - 11:47

Any resolution on this issue, I am seeing the same behaviour with CUPS/CUPC 7 and MPE 2.1

pvarenholt Fri, 09/11/2009 - 11:56

not sure what fix was but recall opening a tac case to fix - sorry.

Actions

This Discussion