Showing results for 
Search instead for 
Did you mean: 

Multi login MOVI ???

Hi all especially TAC person,

is MOVI can't prevent  can multilogin ? because MOVI user can login with same user account in same time. even in my corporate one user account can be use for 5 persons.

i develop MOVI follow the document guide, consist of one TMS, one VCS control, and one VCS expressway.

is there any solution to stop this ?



Andrew Vasel

I am also interested in seeing the official Cisco response to this. Although I would not say it is a problem within our environment, it would be good information to know.

I would also ;love to hear an answer on this. I am asked for every Movi install how to control this. I assume direct Registration contro can work. I assume using AD lookups for accounts can somehow be engaged? maybe not?...although it is common to be able to login to multiple machines with one credential in a domain, so....

Justin Ferello


There is a reason for the multiple logins.  Remember that MOVI is one piece to a growing puzzle called 'Provisioning'.  It is possible for an individual to have multiple endpoints that they need provisioned. 

For example; I have an E60 in the office, an E20 at home and MOVI when I am on the road.  I need all my endpoints to be online at the same time.  My company does not allow direct registrations. 

In this example my company would provide me with (1) username & password that would allow me to log into MOVI and provision my EX60 & E20 without needing to know any other technical information.

In summary, they must allow multiple logins for the Provisioning system to function properly.  However I am not sure why they allow duplicate SIP aliases.



Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

I guess that's what I am interested in seeing: if there is a way to prevent duplicate SIP aliases.

I do not agree that it is a requirement.

First of all, if you have multiple systems with one account (I would anyhow prefer one account per registration,

but that's a personal preference, you could use something like: {username}.{device.model}@domain as the

device uri. Then you have a proper mapping, one registration per device.

You can combine that incely with findme.

In addition there is a risk that you have the same alias on different vcs's (like on the expressway and the control),

which (depending on your search rules), can cause different

There is the possibility to do some magic with server based cpls, but this depends a backend server

and development, which is way to much for most deployments.

I lack both, limit the provisioning and better/easy control / limit of the sip registrations.

Please remember to rate helpful responses and identify

I think it all falls back on the SIP protocol allowing this function….good motivator for FindMe feature…..which makes sense…

Paul E. Thomas, BSEE

Director of Zpro Installations & Advanced Services

Cell: 267-885-8622 | Fax: 215-348-7790 | Video:

Need Zcare Tech Support?

US Tel, 8-8 EST: 215-348-9481 x 206 (after hours, select option 3)

US Toll Free: 1-888-4-ZCARE-4 (1-888-492-2734) | International: 1-215-348-9481

Video Test #: IP zcare@kbz.comString.fromCharCode(122,99,97,114,101,64,107,98,122,46,99,111,109)'?subject=KBZ%20IP%20Video%20test%20%23'> | Email: zcare@kbz.comString.fromCharCode(122,99,97,114,101,64,107,98,122,46,99,111,109)'?subject=KBZ%20IP%20Video%20test%20%23'>



This e-mail transmission (and attachments, if any) contains information exclusively for the intended recipient(s). If you are not an intended recipient you are hereby notified that any forwarding, disclosure, copying, distribution, unauthorized interception of this transmission, or actions based upon the content of this e-mail are prohibited and may be unlawful. If you have received this e-mail transmission in error, promptly notify the sender and destroy all copies. KBZ Communications, Inc. reserves the right to retain, monitor, and intercept emails to and from our system. © 2010 KBZ Communications, Inc., ESD_V1.1

This is not a limitation of the protocol, its dependent on how the sip registrar handles it.

On a registration the location will be saved at the sip registrar, it up to him to decide how many

simultaneous locations for the same URI he supports. I have a registrar running which is limited to one.

btw, Paul. you have plenty of spam below your message.

Please remember to rate helpful responses and identify


Your statement does not make any sense.  I was strictly talking about logins, not registrations.  The OP's question was about how to limit a user from logging in multiple times.  The Device URI has nothing to do with the username/password that you provide the user to log into the VCS via the Provisioning system.

Also, using that Device URI pattern does not stop duplicate SIP entries either.  If I log into MOVI on (2) seperate computers using the same credentials I will still have (2) '' entries on the VCS, since the 'Device Model' is MOVI in both logins.



Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ
Oleksandr Yurchenko

Hi kabiru

You can prevent Movi multilogin.

Don’t use Device URI Pattern.

In this case, you will need to manually write the Device URI, for each new device for Movi.

In this usage, you can control a one device with movi = a one login movi.

It is not convenient, it's not good, this is not applicable for large installation - but it works

Br. Oleksandr

interesting thought, though I would be a bit afraid that the empty device uri has some other

strange side symptoms.

I would also guess that the provisioning itself would even succeed, but it just gets an empty aor

back, ...

It also does not prevent somebody using a 3rd party sip client to register with his movi uri.

Please remember to rate helpful responses and identify


You are correct, having an empty device URI string would not work properly.



Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

You always can test :-)

If you use blank Device URI Pattern, the Movi user can not login. You received:

"Due to registration failure. If the problem persists contact IT support."

You must manually write Device URI for each device for a successful login .


Hi Oleksandr,

thanks for your help, but maybe if we talk about this in the lab it can be approved, but unfortunately we are working in the real world, where MOVI always used for medium-large deployment for many users, is there any solutions beside

manually write the Device URI. you can imagine how big the effort if we use your solution



Ahmad Kabiru

Hi Ahmad

I am agree with you about big effort for this solution.

I am agree Its not good decision.

But i dont know another way, to prevent multiple login.

br. oleksandr

Recognize Your Peers
Content for Community-Ad