CUCiMOC - No Phone Number associated when trying to place a call to MOC

Unanswered Question
Sep 22nd, 2009

Hi we have recently installed CUCIMOC in a pilot for my company. I have everyhting working apart from beign able to drag a contact to place a call. I am running CUCM v6.1.4 and OCS 2007 R2. The simple problem is that I get an error message when I try to call a "MOC" client only. I know that 6.1(4) is not E.164 compatible but thought there was a workaround with the Application Dial Rules but I have implemented but still not working. I can call a MOC user by dialling the number but would like to be able to simply right click and call or just drag and drop. Any ideas would be appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
UCcomp2007 Tue, 09/22/2009 - 08:42

Couple of questions for clarification. Sounds like your attempting mutliple things here (CUCIMOC functionality and UCM direct to OCS calls).

1. Do you have a sip trunk between OCS and CUCM?

2. Do MOC users have + sign in front of phone number?

3. You say you can dial from UCM to MOC user directly, what is the number you dial direct?

4. Can MOC only user call cisco ip phone?

cmcinally Tue, 09/22/2009 - 10:02

Hi UComp2007,

1. We have a working SIP trunk between OCS & CUCM.

2. MOC users have a + sign in front of their number in OCS but not in AD.

3. MOC Users have extensions 79XX IP Phones 78XX. The number I dial direct is 7900.

4. MOC users can dial IP phones no problem. We have a mediation server in place. There is also normalisation rules on the OCS.

UCcomp2007 Wed, 09/23/2009 - 03:25

Are you using CUCIMOC softphone, or using CUCIMOC to control hardphone? If controlling hardphone, what is phone model. Type A phones (7940, 7960) can't deal with + sign.

If your using CUCIMOC softphone, I would run wireshark on MOC users pc to see what digits are being passed, and also to see if application dial rule is being invoked.

UCM 6.x does not have support for dealing with + sign, so i'm wondering even though you have the application dial rule setup, if UCM can strip that + sign.

We have this all setup in similar fashion on UCM 7 and have no issues (but UCM 7 does have full support for dialing normalization and dealing with + sign).

Regards,

cmcinally Fri, 09/25/2009 - 11:33

I am actually using CUCIMOC to control both but I am simply using the softphone when using drag to call. I have created the Application dial rule to strip the + which is being invoked as I can actually dial one MOC only user using drag to Call. I tried running wireshark to take a sniffer trace but could not see any digits being passed so I do not know if CUCIMOC is even getting that far. I suspect this may be something to do with AD users numbers not being in E.164 format despite OCS using normalisation. I also got a login for the OCS Server and found several errors relating to AD E.164 and OCS Address Book errors. I will let you knwo how I get on as I am continuing to work on it.

shane.orr Sat, 09/26/2009 - 17:59

Maybe I am barking up a wrong tree here but it is my understanding that you do not have + E.164 numbers in AD. I recently had a CUCiMOC pilot for a customer who did not want to format their numbers in AD either. Their format in the Telephone Field was XXX-XXX-XXX and had 4 digit internal extensions in Call Manager. I ended up normalizing OCS so when I dragged a call to a contact the dialed number was normalized before it is dialed. I was a little overwhelmed at first because I had never configured OCS. I finally found this blogged that helped out tremendously.

http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=26

Otherwise if I did not normalize in OCS I would have to had created 10 digit to 4 digit translation patterns in Call Manager did not want to do that because I would start to have an overlapping dial plan.

Hope that makes sense...

htluo Sat, 09/26/2009 - 04:50

CUCIMOC does not require SIP trunk between OCS and CUCM.

CUCIMOC gets the phone number from MOC and requires E.164 format.

If you got "no phone number associated", you should troubleshoot MOC/OCS.

Steps to Resolve

* Make sure the Address book Synchronize error is not displayed on MOC.

* If the error is displayed , follow the link here to resolve it.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/7_1/english/integrat/guide/troubleshooting.html#wp1055785

* If MOC checks out for above (Address book Synchronize error is not displayed on MOC), then perform a manual sync of OCS to its LDAP

o Manually Sync OCS address book

Open cmd prompt on OCS Server and type the following,

* cd C:\Program Files\Microsoft Office Communications Server 2007\Server\Core

* C:\Program Files\Microsoft Office Communications Server 2007\Server\Core\abserver -syncnow

Delete your local copy of MOC Database - GalContacts.db

* C:\Documents and Settings\\Local Settings\Application Data\Microsoft\Communicator\GalContacts.db file

http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/7_1/english/integrat/guide/config_servers.html#wp1053260

* If MOC Client still contains wrong information, then delete local copy of GalContacts.db

o Exit out of MOC

o XP - C:\Documents and Settings\\Local Settings\Application Data\Microsoft\Communicator

o Vista - C:\Users\\AppData\Local\Microsoft\Communicator

Hope this helps.

Michael

http://htluo.blogpsot.com

Actions

This Discussion