Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MiCollab 6 USP - MAC Address already exists in the system

Status
Not open for further replies.

bribob

Technical User
Joined
Jun 1, 2007
Messages
170
Location
CA
vMiCollab 6.0.41.0

I'm attempting to manually provision a user in MiCollab. I am able to create the user but I encounter an error when entering the MAC address of the phone.

'Create Phone Service Error. The MAC Address already exists in the system'

I have checked the MCD, the MAC address is not in use. I have manually built the phone in MCD and successfully assigned the MAC address, which tells me that the MCD is not the source of the error. I suspect that a user already exists in USP, that this MAC address is assigned to.

There must be a way to check the postgres DB within MiCollab to see which user/phone has this MAC address assigned, does anyone know where I should start looking? Is there a CLI command that will dump the entire USP DB, not just the username/email/DN/services list?


-b
 
Oh my!

Is it possible the Mac is on a different system?

Have you / can you program without the MAC, I don't think I ever bother as I prefer PIN registration.

**********************************************
What's most important is that you realise ... There is no spoon.
 
That's what I suspected, so I started my investigation by logging into all MCDs in the cluster and checked, didn't find the MAC address.

I disabled Single Point Provisioning and the error remained. I was also able to manually configure the DN/MAC in the MCD it was accepted, so the phone could technically register and all would be well, except that I would know there is a disturbance in The Force (MiCollab and MCD DB out of sync).

I found the MAC address in the UPM/current log, below is the reference to the error:

UPM: pgSQLObj.cpp(589): pgSQLObj.cpp: INSERT INTO msvc_ICP3300PhoneServiceDataList (output omitted / details about the phone)
UPM: pgSQLObj.cpp(608): pgSQLObj.cpp: Unable to insert child (msvc_ICP3300PhoneServiceDataList): - ERROR: duplicate key value violates unique constraint "u_msvc_icp3300phoneservicedatalist_macaddress"
UPM: pgErrorObj.cpp(141): pgErrorObj.cpp: *** Found duplicate key string
UPM: pgErrorObj.cpp(156): pgErrorObj.cpp: duplicate key value violates unique constraint "u_msvc_icp3300phoneservicedatalist_macaddress"
UPM: pgErrorObj.cpp(168): pgErrorObj.cpp: Extracted constraint name
UPM: pgErrorObj.cpp(169): pgErrorObj.cpp: u_msvc_icp3300phoneservicedatalist_macaddress
UPM: PostgresAdapter.cpp(3248): PostgresAdapter.cpp: PGAdapter: Rollback Successful


Yes, I know I should have paid more attention in Database class.


-b
 
To answer your question, yes I can add the DN to the user in MiCollab without the MAC address.


-b
 
But adding without mac affects other applications?

**********************************************
What's most important is that you realise ... There is no spoon.
 
does it have an entry in the teleworker database

If I never did anything I'd never done before , I'd never do anything.....

and due to an endless stream of MiCollab , MiCC issues
Life would be simpler If only they tested products properly before releasing them .....
 
@kwb - Added the phone without MAC, have also assigned NuPoint mailbox, MDuG, TW service w/o MAC

@Bill - Checked the Teleworker DB in MiCollab and the 2 MBG's in the cluster. No MAC found


-b
 
the mac is programmed in the teleworker ...
delete it in the MBG.. and it should work fine
 
Mitel TS took a backup of the MAS DB and used a tool to find the offending MAC assigned to another user. It would appear that the MBG DB and USP DB are separate.


-b
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top