Can't dial Jabber (Movi) clients or iPad Jabber Video addresses

palves · ‎07-31-2012

Hi All,

I'm having an issue where I can not dial the main video address of users using FindMe (I can dial their username.devicetype@domain.com address - it works, but not the firstname.lastname@domain.com video address).

Basically, I've noticed that users registering to either the VCS Expressway or VCS Control register using their username.devicetype@domain.com addresses.

I assume if it was working properly, they would register using their firstname.lastname@domain.com addresses.

The Caller-ID appears to be working correctly, shows their video address when a call is made (firstname.lastname@domain.com).

If I log in the user using Jabber 4.4 on a laptop it will register as username.movi@domain.com.

If I log in the same user using jabber on an iPad, it will register as username.jabbertablet@domain.com

When I try to dial them using firstname.lastname@domain.com, it doesn't work at all (can't find the user).

I can reach their username.devicetype@domain.com addresses - this works.

I can log into the users FindMe page, and see it should be trying Jabber on the laptop first, then Jabber for iPad for that user.

I switched it around, but nothing - doesn't change the fact that I can't dial a users video address (firstname.lastname@domain.com)

Anyone have any ideas? (yes my group setting bound to the users has their video address in the format firstname.lastname@domain.com)

thanks!

Paul

Martin Koch · ‎07-31-2012

Hi!

Your devices will behave and register as you have configured it in the provisioning directory.

The devices itself shall register to something different then the findme name, so thats ok.

Findme will make the binding in between the devices and the findme address.

It can be that your findme template is not ok or that you lack some search rules.

I would recomend that you check on the provisioning deployment guide to better understand

how it shall work.

Please remember to rate helpful responses and identify

palves · ‎08-01-2012

Hi Martin,

Not sure what search rules would fix this (I can dial the device addresses no problem).

thanks,

Paul

Alok Jaiswal · ‎08-01-2012

Hi Paul,

what is the configuration you have under provisioning directory?

if the device uri pattern is {username}{device.model} then the registration would be username.device only.

what is the video-address pattern you defined on provisioning directory?

Thanks

Alok

palves · ‎08-01-2012

Hi Alok,

The device address pattern is {username}{device.model}, I attached a screen shot.

If its suppose to be this way (that devices will then registerd to VCS with {username}{device.model}, that's fine.

But I still can't reach people using the video address pattern which is {firstname.lastname}, see attached screen shot

Also, I'm using TMS 13.1 and Provisioning Extensions (not legacy)

gubadman · ‎08-01-2012

Hi,

What devices are in the users FindMe active location, under Systems > Provisioning > FindMe on TMS

e.g.

Are the devices you expect listed in the active profile?

Systems Provisioning FindMe

palves · ‎08-01-2012

Here's an attachment of what I have configured for myself.

And yes, the devices I expect are listed in the active profile.

thanks,

Paul

Martin Koch · ‎08-01-2012

In general that looks ok. When you login to the VCS itself, you can see these user accounts?

(as you write it rewrites the source address it seem to be working)

If not check that the sip server address uses the cluster name and that the TMSPE also replicates

the folder to the VCS.

On the VCS you also have some debugging capability to check on what is replicated to the VCS.

Remember that this address will only be found on the VCS which runns findme.

Like you have a call from the internet, it goes to the VCS-E without findme, then

to the VCS-C with findme where it finds it and then to the address it looked up.

If you could tell us a bit more about the deployment, the call flow for the failed call and post

a search history of that call, maybe we can say something more then.

Please remember to rate helpful responses and identify

palves · ‎08-01-2012

Hi Martin,

On my VCS Control (only have 1 of them), if I do a search by REGISTRATION/ALIAS, I can see them registered as username.devicetype@domain.com (in that format). Not sure if you mean by "can see these user accounts" exactly.

I was able to see the following....

How can I check if its being replicated to VCS? I checked the findMe TMSPE service status in VCS and its Active, don't see any issues there at least.

I've tried using findMe from devices just connected to the VCS Control.

In my environment basically there is 1 VCS Control on the inside and 1 VCS Expressway on the outside.

Regardless of where the endpoints are located, I can not reach users through their Video address in the format firstname.lastname@domain.com, only by their username.devicetype@domain.com names.

thanks,

Paul

Martin Koch · ‎08-01-2012

To debug the TMSPE its good to start at:

System > TMS Provisioning Extension services

https:///tmsservices

And take a look at the findme location config

https:///findmelocationconfig

If this is ok check the search history and rules. Maybe you strip, add, not search or exclude something

You know this is one of the typical cases where its either firing in the blind or it most likely takes way more

time to explain then to look at it.

Ask your Cisco TelePresence partner. This is a perfect case for him to look at, a remote session if possible should be fine.

Please remember to rate helpful responses and identify

Alok Jaiswal · ‎08-02-2012

Hi Paul,

we are interested to know when you make a call using the findme id what is the error it shows under VCS.

can you paste a search of this call from VCS?

Thanks

Alok

Patrick Pettit · ‎08-03-2012

HI palves. If you can confirm for us that Find Me is enabled on VCS would be helpful. Applications>Find Me>Configuration.

You should see a search and subsearches looking for the devices that are a part of the find me setup.

Find me ID is papettit@tac.lab. If you don't see the Admin Policy Find Me in your search history, I'd verify that its enabled on the VCS. This is an example from our lab calling my find me account with MOVI and an E20 registered to CUCM:

Search (279)
- State: Completed
- Found: True
- Type: SIP (INVITE)
- CallRouted: True
- CallSerial Number: 550d9b7c-dd65-11e1-b716-0010f30f5600
- Tag: 550d9cb2-dd65-11e1-bfbd-0010f30f5600
- StartTime: 2012-08-03 08:18:28
- Duration: 4.68
- Source (1)
- - Authenticated: True
- - Aliases (1)
  - - Alias (1)
    - - Type: Url
    - - Origin: Unknown
    - - Value: patrick.pettit.1700.sip@tac.lab
- - Zone (1)
  - - Name: LocalZone
  - - Type: Local
- - Path (1)
  - - Hop (1)
    - - Address: x.x.x.x:5061
- Destination (1)
- - Alias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: sip:papettit@tac.lab
- SubSearch (1)
- - Type: Transforms
- - Action: Not Transformed
- - ResultAlias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: papettit@tac.lab
- - SubSearch (1)
  - - Type: Admin Policy
  - - Action: Proxy
  - - ResultAlias (1)
    - - Type: Url
    - - Origin: Unknown
    - - Value: papettit@tac.lab
  - - SubSearch (1)
    - - Type: FindMe
    - - Action: Proxy
    - - ResultAliases (1)
      - Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: papettit.movi@tac.lab
      - Alias (2)
        
        Type: Url
        
        Origin: Unknown
        
        Value: papettit@tac.lab
    - - SubSearch (1)
      - Type: Transforms
      - Action: Not Transformed
      - ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: papettit.movi@tac.lab
      - SubSearch (1)
        
        Type: Admin Policy
        
        Action: Proxy
        
        ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: papettit.movi@tac.lab
        
        SubSearch (1)
        
        Type: FindMe
        
        Action: Proxy
        
        ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: papettit.movi@tac.lab
        
        SubSearch (1)
        
        Type: Search Rules
        
        SearchRule (1)
        
        Name: Localzone AnyAlias
        
        Zone (1)
        
        Name: LocalZone
        
        Type: Local
        
        Protocol: SIP
        
        Found: False
        
        Reason: busy here
        
        Gatekeeper (1)
        
        Address: x.x.x.x
        
        Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: papettit.movi@tac.lab
    - - SubSearch (2)
      - Type: Transforms
      - Action: Not Transformed
      - ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 991004@tac.lab
      - SubSearch (1)
        
        Type: Admin Policy
        
        Action: Proxy
        
        ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 991004@tac.lab
        
        SubSearch (1)
        
        Type: FindMe
        
        Action: Proxy
        
        ResultAlias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 991004@tac.lab
        
        SubSearch (1)
        
        Type: Search Rules
        
        SearchRule (1)
        
        Name: VCS To CUCM 9 With Domain
        
        Zone (1)
        
        Name: Trunk to CUCM 9
        
        Type: Neighbor
        
        Protocol: SIP
        
        Found: True
        
        Gatekeeper (1)
        
        Address: x.x.x.x:5060
        
        Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 991004@tac.lab