Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2102
Views
15
Helpful
12
Replies

movi to movi not working

Go to solution
born.jason
Level 1
Level 1

‎01-15-2013 06:09 AM - edited ‎03-18-2019 12:26 AM

Hi,

scenario:

Jabber Video (external) -> VCS-E -> VCS-C (Active Directory Service) -> TMSPE (user imported from LDAP)

user1@testdomain.com calls user2@testdomain.com both provisioned with TMSPE and online with Jabber Video.

See here a call leg from VCS-E:

    Search (349)
        State: Completed
        Found: False
        Reason: Proxy Authentication Required
        Type: SIP (INVITE)
        CallSerial Number: 39d4d3f6-5f1b-11e2-9206-0010f3249cce
        Tag: 39d4d590-5f1b-11e2-99ec-0010f3249cce
        Source (1)
            Authenticated: False
            Aliases (1)
                Alias (1)
                    Type: Url
                    Origin: Unknown
                    Value: user1.movi@testdomain.com
            Zone (1)
                Name: DefaultSubZone
                Type: Local
            Path (1)
                Hop (1)
                    Address: 192.168.5.10:56075
        Destination (1)
            Alias (1)
                Type: Url
                Origin: Unknown
                Value: sip:user2@testdomain.com
        StartTime: 2013-01-15 14:55:31
        Duration: 0.07
        SubSearch (1)
            Type: Transforms
            Action: Not Transformed
            ResultAlias (1)
                Type: Url
                Origin: Unknown
                Value: user2@testdomain.com
            SubSearch (1)
                Type: Admin Policy
                Action: Proxy
                ResultAlias (1)
                    Type: Url
                    Origin: Unknown
                    Value: user2@testdomain.com
                SubSearch (1)
                    Type: FindMe
                    Action: Proxy
                    ResultAlias (1)
                        Type: Url
                        Origin: Unknown
                        Value: user2@testdomain.com
                    SubSearch (1)
                        Type: Search Rules
                        SearchRule (1)
                            Name: Traversal zone search rule
                            Zone (1)
                                Name: TraversalZone
                                Type: TraversalServer
                                Protocol: SIP
                                Found: False
                                Reason: Proxy Authentication Required
                                StartTime: 2013-01-15 14:55:31
                                Duration: 0.02
                                Gatekeeper (1)
                                    Address: 10.10.40.18:25006
                                    Alias (1)
                                        Type: Url
                                        Origin: Unknown
                                        Value: user2@testdomain.com
                            Zone (2)
                                Name: TraversalZone
                                Type: TraversalServer
                                Protocol: H323
                                Found: False
                                Reason: Not registered - Destination not found
                                StartTime: 2013-01-15 14:55:31
                                Duration: 0.04
                                Gatekeeper (1)
                                    Address: 10.10.40.18:1719
                                    Alias (1)
                                        Type: Url
                                        Origin: Unknown
                                        Value: user2@testdomain.com

and here VCS-C:

    Search (76)
        State: Completed
        Found: False
        Reason: Not found
        Info: Policy Response
        Type: SIP (INVITE)
        CallSerial Number: 5f2adfdc-5f1c-11e2-8afc-0010f3249b3a
        Tag: 5f276780-5f1c-11e2-ac63-0010f3249cce
        Source (1)
            Authenticated: True
            Aliases (1)
                Alias (1)
                    Type: Url
                    Origin: Unknown
                    Value: user1.movi@testdomain.com
            Zone (1)
                Name: TraversalZone
                Type: TraversalClient
            Path (1)
                Hop (1)
                    Address: 194.123.45.67:7001
                Hop (2)
                    Address: 192.168.5.10:56075
        Destination (1)
            Alias (1)
                Type: Url
                Origin: Unknown
                Value: sip:user2@testdomain.com
        StartTime: 2013-01-15 15:03:43
        Duration: 0.12
        SubSearch (1)
            Type: Transforms
            Action: Transformed
            ResultAlias (1)
                Type: H323Id
                Origin: Unknown
                Value: user2@testdomain.com
            SubSearch (1)
                Type: Admin Policy
                Action: Proxy
                ResultAlias (1)
                    Type: H323Id
                    Origin: Unknown
                    Value: user2@testdomain.com
                SubSearch (1)
                    Type: FindMe
                    Action: Proxy
                    ResultAlias (1)
                        Type: H323Id
                        Origin: Unknown
                        Value: user2.movi@testdomain.com
                    SubSearch (1)
                        Type: Transforms
                        Action: Not Transformed
                        ResultAlias (1)
                            Type: H323Id
                            Origin: Unknown
                            Value: user2.movi@testdomain.com
                        SubSearch (1)
                            Type: Admin Policy
                            Action: Proxy
                            ResultAlias (1)
                                Type: H323Id
                                Origin: Unknown
                                Value: user2.movi@testdomain.com
                            SubSearch (1)
                                Type: FindMe
                                Action: Proxy
                                ResultAlias (1)
                                    Type: H323Id
                                    Origin: Unknown
                                    Value: user2.movi@testdomain.com
                                SubSearch (1)
                                    Type: Search Rules
                                    SearchRule (1)
                                        Name: Traversal zone search rule
                                        Zone (1)
                                            Name: TraversalZone
                                            Type: TraversalClient
                                            Protocol: SIP
                                            Found: False
                                            Reason: Not found
                                            StartTime: 2013-01-15 15:03:43
                                            Duration: 0.07
                                            Gatekeeper (1)
                                                Address: 194.123.45.67:7001
                                                Alias (1)
                                                    Type: H323Id
                                                    Origin: Unknown
                                                    Value: user2.movi@testdomain.com
                                        Zone (2)
                                            Name: TraversalZone
                                            Type: TraversalClient
                                            Protocol: H323
                                            Found: False
                                            Reason: Not registered - Destination not found
                                            StartTime: 2013-01-15 15:03:43
                                            Duration: 0.01
                                            Gatekeeper (1)
                                                Address: 194.123.45.67:6001
                                                Alias (1)
                                                    Type: H323Id
                                                    Origin: Unknown
                                                    Value: user2.movi@testdomain.com

I have the feeling there is a loop because at the end on vcs-c it goes to the traversal zone?

Any help?

Regards

Jason

Labels:
0 Helpful
2 Accepted Solutions

Accepted Solutions

Go to solution
rasimyigit
Level 1
Level 1

‎01-18-2013 11:34 PM

Hi,
Normale you dont Need add the sip domain on Vcse . And what is the sip proxy settings on the Vcse? It must " proxy to known or all" . Do check this settings. All zones on the Vcse must be on" do not check credentials". And a search rule like any to VCS-c

Sent from Cisco Technical Support iPhone App

View solution in original post

0 Helpful

Go to solution
Martin Koch
VIP Alumni
VIP Alumni
In response to born.jason

‎01-20-2013 02:12 PM

If you intend to have the call from the VCS-E in the VCS-C and then back to the VCS-E you might

need to disable the loop detection of both VCS.

You find that under:  VCS configuration > Calls

But this might have some site effects, so you should have full control over your search rules.

Maybe you should ask your Cisco Partner or an external consultant to help you.

If you have a standard mapping of your movi users you could also add a search rule

replicating what the findme account is doing on the VCS-C so the call is directly matched

on the VCS-E or use findme or a CPL/Policy server to handle the calls.

Please remember to rate helpful responses and identify

View solution in original post

0 Helpful
12 Replies 12

Go to solution
Martin Koch
VIP Alumni
VIP Alumni

‎01-15-2013 07:33 AM

If you could tell us a bit more about your deployment.

Like where are your sip domains added (vcs-c or also vcs-e)

How is your setup of the findme uri, device uri.

Where is the device provisioning and findme installed.

How would you expect the call flow to take place?

How do your search rules and transforms look like?

How do your authentication settings look like? (its a bit strange to see the proxy auth error on the VCS-E but nothing in the sip part of the VCS-C log)

If the sip domain is only added on the VCS-C and you do a proxy registration.

Do you see the movi registration on the VCS Registration by Device list?

How do your search rules look like on the VCS-C targeting the local zone?

What do you allow as the "source" for the search rule targeting the local zone?

If its local zone, could you try with "any" or "AllZones"

Did you follow the deployment guide?

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.pdf

Please remember to rate helpful responses and identify

Go to solution
born.jason
Level 1
Level 1
In response to Martin Koch

‎01-17-2013 03:13 AM 

Like where are your sip domains added (vcs-c or also vcs-e)

The SIP domains are configured on the VCS-C and VCE-E. Both the same domain.

How is your setup of the findme uri, device uri.

The setup of findeme uri and device uri is configured on the TMSPE server.

Where is the device provisioning and findme installed.

I have installed a TMS (14.1.1) server with TMSPE and TMSXE. I have a findme device template which is configured with device address pattern -> {username}.jabbervideo@testdomain.com

For the User i have a video address pattern -> {first_name}.{last_name}@testdomain.com

and a device adress pattern -> {username}.{device.model}@testdomain.com

If i log in from external i can see an active device under TMS - Systems -Provisioning - Devices with video address -> user1.movi@testdomain.com

How would you expect the call flow to take place?

In my opinion, i log in from outside dial another movi user with user2@testdomain.com and the call should go from Internet -> VCS-E -> VCS-C -> lookup in TMS -> VCS-C/E ? (Depending on where the user is logged in with Jabber Video (internal/external) )

How do your search rules and transforms look like?

i have some transforms and search rules configured on VCS-C. But i think no for movi to movi. Should there some configured?  

How  do your authentication settings look like? (its a bit strange to see  the proxy auth error on the VCS-E but nothing in the sip part of the  VCS-C log)

on VCS-C i have set Default Zone, Traversal Zone, Default Subzone to "check credentials"

I have configured a Subzone "Local VCSC Zone" with treat as authenticated.

on VCS-E i have set Default Zone,TraversalZone, Default Subzone to "do not check crredentials"

If the sip domain is only added on the VCS-C and you do a proxy registration.

sip domain is added to both

Do you see the movi registration on the VCS Registration by Device list?

yes, on VCS-E i see "user1.movi@testdomain.com"

How do your search rules look like on the VCS-C targeting the local zone?

I have only one search rule von VCS-C configured targeting the local zone and this is from CUCM to VCSC (FROM CUCM to VCSC Registered Devices)

Protocol: Any

Source: Any

Request must be authenticated: no

mode: alias pattern match

pattern type: Regex

pattern string: (.*)@((:|;).*)?

Pattern behavior: replace

Replace string: \1@testdomain.com

On successful match: stop

Target: LocalZone

What do you allow as the "source" for the search rule targeting the local zone?

Any

If its local zone, could you try with "any" or "AllZones"

i tried this. Nu success.

Did you follow the deployment guide?

Yes i did.

Device Address Pattern:
0 Helpful

Go to solution
Alok Jaiswal
Cisco Employee
Cisco Employee
In response to born.jason

‎01-17-2013 04:13 AM

Hi Born,

is this issure simillar to this thread posted by you.?

https://supportforums.cisco.com/message/3830069#3830069

if the movi/jabber client registration is on VCS-exp under default subzone or specific subzone can you make it as "treat as authenticated" and try again.

Regards

Alok

Go to solution
born.jason
Level 1
Level 1
In response to Alok Jaiswal

‎01-17-2013 05:07 AM

Yes its the same. Sorry i noticed to late that i posted it double. :-/

So, i have now some oter input. I tried to call from an external registered movi client to an internal registered movi client. On VCS-E under device registration i see the external movi client and on VCS-C i see the internal movi client registered.

Here are now the call legs if i try to dial from external to internal movi client.

VCS-Express

2x SIP searches from 1 dialing

    Search (253)

        State: Completed

        Found: False

        Reason: Not found

        Info: Policy Response

        Type: SIP (INVITE)

        CallSerial Number: 2ecfb8ba-60a4-11e2-ba28-0010f3249cce

        Tag: 2ecfba5e-60a4-11e2-8f49-0010f3249cce

        Source (1)

            Authenticated: True

            Aliases (1)

                Alias (1)

                    Type: Url

                    Origin: Unknown

                    Value: user1.movi@testdomain.com

            Zone (1)

                Name: DefaultSubZone

                Type: Local

            Path (1)

                Hop (1)

                    Address: 192.168.5.10:50449

        Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:user2.movi@testdomain.com

        StartTime: 2013-01-17 13:48:25

        Duration: 0.2

        SubSearch (1)

            Type: Transforms

            Action: Not Transformed

            ResultAlias (1)

                Type: Url

                Origin: Unknown

                Value: user2.movi@testdomain.com

            SubSearch (1)

                Type: Admin Policy

                Action: Proxy

                ResultAlias (1)

                    Type: Url

                    Origin: Unknown

                    Value: user2.movi@testdomain.com

                SubSearch (1)

                    Type: FindMe

                    Action: Proxy

                    ResultAlias (1)

                        Type: Url

                        Origin: Unknown

                        Value: user2.movi@testdomain.com

                    SubSearch (1)

                        Type: Search Rules

                        SearchRule (1)

                            Name: Traversal zone search rule

                            Zone (1)

                                Name: TraversalZone

                                Type: TraversalServer

                                Protocol: SIP

                                Found: False

                                Reason: Not found

                                StartTime: 2013-01-17 13:48:25

                                Duration: 0.15

                                Gatekeeper (1)

                                    Address: 10.10.40.18:25007

                                    Alias (1)

                                        Type: Url

                                        Origin: Unknown

                                        Value: user2.movi@testdomain.com

                            Zone (2)

                                Name: TraversalZone

                                Type: TraversalServer

                                Protocol: H323

                                Found: False

                                Reason: Not registered - Destination not found

                                StartTime: 2013-01-17 13:48:25

                                Duration: 0.04

                                Gatekeeper (1)

                                    Address: 10.10.40.18:1719

                                    Alias (1)

                                        Type: Url

                                        Origin: Unknown

                                        Value: user2.movi@testdomain.com

    Search (254)

        State: Completed

        Found: False

        Reason: Not found

        Info: Policy Response

        Type: SIP (INVITE)

        CallSerial Number: 2edadcc2-60a4-11e2-84b4-0010f3249cce

        Tag: 2ecfba5e-60a4-11e2-8f49-0010f3249cce

        Source (1)

            Authenticated: True

            Aliases (1)

                Alias (1)

                    Type: Url

                    Origin: Unknown

                    Value: user1@testdomain.com

            Zone (1)

                Name: TraversalZone

                Type: TraversalServer

            Path (1)

                Hop (1)

                    Address: 10.10.40.18:5061

                Hop (2)

                    Address: 194.123.45.67:7001

                Hop (3)

                    Address: 192.168.5.10:50449

        Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:user2.movi@testdomain.com

        StartTime: 2013-01-17 13:48:25

        Duration: 0

        SubSearch (1)

            Type: Transforms

            Action: Not Transformed

            ResultAlias (1)

                Type: Url

                Origin: Unknown

                Value: user2.movi@testdomain.com

            SubSearch (1)

                Type: Admin Policy

                Action: Proxy

                ResultAlias (1)

                    Type: Url

                    Origin: Unknown

                    Value: user2.movi@testdomain.com

                SubSearch (1)

                    Type: FindMe

                    Action: Proxy

                    ResultAlias (1)

                        Type: Url

                        Origin: Unknown

                        Value: user2.movi@testdomain.com

                    SubSearch (1)

                        Type: Search Rules

VCS-Control

1x SIP searches from 1 dialing

    Search (154)

        State: Completed

        Found: False

        Reason: Not found

        Info: Policy Response

        Type: SIP (INVITE)

        CallSerial Number: 2ed3bc3a-60a4-11e2-ba84-0010f3249b3a

        Tag: 2ecfba5e-60a4-11e2-8f49-0010f3249cce

        Source (1)

            Authenticated: True

            Aliases (1)

                Alias (1)

                    Type: Url

                    Origin: Unknown

                    Value: user1.movi@testdomain.com

            Zone (1)

                Name: TraversalZone

                Type: TraversalClient

            Path (1)

                Hop (1)

                    Address: 194.123.45.67:7001

                Hop (2)

                    Address: 192.168.5.10:50449

        Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:user2.movi@testdomain.com

        StartTime: 2013-01-17 13:48:25

        Duration: 0.11

        SubSearch (1)

            Type: Transforms

            Action: Transformed

            ResultAlias (1)

                Type: H323Id

                Origin: Unknown

                Value: user2.movi@testdomain.com

            SubSearch (1)

                Type: Admin Policy

                Action: Proxy

                ResultAlias (1)

                    Type: H323Id

                    Origin: Unknown

                    Value: user2.movi@testdomain.com

                SubSearch (1)

                    Type: FindMe

                    Action: Proxy

                    ResultAlias (1)

                        Type: H323Id

                        Origin: Unknown

                        Value: user2.movi@testdomain.com

                    SubSearch (1)

                        Type: Transforms

                        Action: Not Transformed

                        ResultAlias (1)

                            Type: H323Id

                            Origin: Unknown

                            Value: user2.movi@testdomain.com

                        SubSearch (1)

                            Type: Admin Policy

                            Action: Proxy

                            ResultAlias (1)

                                Type: H323Id

                                Origin: Unknown

                                Value: user2.movi@testdomain.com

                            SubSearch (1)

                                Type: FindMe

                                Action: Proxy

                                ResultAlias (1)

                                    Type: H323Id

                                    Origin: Unknown

                                    Value: user2.movi@testdomain.com

                                SubSearch (1)

                                    Type: Search Rules

                                    SearchRule (1)

                                        Name: Traversal zone search rule

                                        Zone (1)

                                            Name: TraversalZone

                                            Type: TraversalClient

                                            Protocol: SIP

                                            Found: False

                                            Reason: Not found

                                            StartTime: 2013-01-17 13:48:25

                                            Duration: 0.06

                                            Gatekeeper (1)

                                                Address: 194.123.45.67:7001

                                                Alias (1)

                                                    Type: H323Id

                                                    Origin: Unknown

                                                    Value: user2.movi@testdomain.com

                                        Zone (2)

                                            Name: TraversalZone

                                            Type: TraversalClient

                                            Protocol: H323

                                            Found: False

                                            Reason: Not registered - Destination not found

                                            StartTime: 2013-01-17 13:48:25

                                            Duration: 0.02

                                            Gatekeeper (1)

                                                Address: 194.123.45.67:6001

                                                Alias (1)

                                                    Type: H323Id

                                                    Origin: Unknown

                                                    Value: user2.movi@testdomain.com


0 Helpful

Go to solution
born.jason
Level 1
Level 1
In response to born.jason

‎01-17-2013 05:30 AM

I have tried it now also from external to external movi.

Bot the same in the search history -> "Not Found"

The Proxy Auth issue has gone. Don`know exactly why...

Any suggestion what i have missing to configure ?

0 Helpful

Go to solution
Alok Jaiswal
Cisco Employee
Cisco Employee
In response to born.jason

‎01-17-2013 07:45 AM

Hi Born,

407 proxy authentication required  coming because your default subzone was in "do not check credentials".

anyways the search is getting complete now but i want to ask what exactly your are dialing ?? user2.moviz@domain or user2@domain?

because i think your requirement is to dial user2@domain isn't it?

if yes, then why the vcs-exp search is showing destination as user2.movi@domain

Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:user2.movi@testdomain.com

        StartTime: 2013-01-17 13:48:25

you should dial user2@domain and if findme is configured correctly it will automatically be taken care.

regds

Alok

Go to solution
born.jason
Level 1
Level 1
In response to Alok Jaiswal

‎01-17-2013 08:28 AM

This is what i thougt too. You are right if you say i have to dial user2@testdomain.com. I think the user2.movi@testdomain.com comes from TMS - Provisioning - User -> Device Address Pattern ?

Should i change this to the same like Video Address Pattern?

But as you see there are two searches if i try to dial this user? One with .movi and one without.

0 Helpful

Go to solution
born.jason
Level 1
Level 1
In response to born.jason

‎01-18-2013 04:01 AM

Hi Alok, any idea?

0 Helpful

Go to solution
Martin Koch
VIP Alumni
VIP Alumni
In response to born.jason

‎01-20-2013 02:12 PM

If you intend to have the call from the VCS-E in the VCS-C and then back to the VCS-E you might

need to disable the loop detection of both VCS.

You find that under:  VCS configuration > Calls

But this might have some site effects, so you should have full control over your search rules.

Maybe you should ask your Cisco Partner or an external consultant to help you.

If you have a standard mapping of your movi users you could also add a search rule

replicating what the findme account is doing on the VCS-C so the call is directly matched

on the VCS-E or use findme or a CPL/Policy server to handle the calls.

Please remember to rate helpful responses and identify

0 Helpful

Go to solution
rasimyigit
Level 1
Level 1

‎01-18-2013 11:34 PM

Hi,
Normale you dont Need add the sip domain on Vcse . And what is the sip proxy settings on the Vcse? It must " proxy to known or all" . Do check this settings. All zones on the Vcse must be on" do not check credentials". And a search rule like any to VCS-c

Sent from Cisco Technical Support iPhone App

0 Helpful

Go to solution
born.jason
Level 1
Level 1
In response to rasimyigit

‎01-24-2013 04:39 AM

Sorry for late respone. I wass offline the last days. I will try this after next week as i`m goging for Cisco Live.

I will give you feedback as soon as possible.

0 Helpful

Go to solution
born.jason
Level 1
Level 1
In response to born.jason

‎03-06-2013 01:48 PM

Just to close this.

There was missing a search rule for local zone on vcs-c and also on vcs-e if a external movi is connected. Thanks for your help.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents