cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
2855
Views
0
Helpful
8
Replies
Peter Anders
Beginner

External Calling through VCS Expressway

I need to get external calling working through the VCS expressway however I am experieincing some issues . My networks team have opened ports up for SIP through to the external IP address however I am still experencing some issues. I have these below

1. Jabber Clients - I have created Jabber clients through TMS and the clients are authenicated in the local DB on the VCS Control. When I try to log inot that account externally I am getting errors saying that the username /password / domian are incorrect however I know that these are correct . I have configured the Internal /External address to the external IP address of the VCSe and the SIP domain to the domain that is configured on the VCSe..( video.XXXX.com.au).

I have checked through all of the zones and dial plans and they all appear correct and allow authenication through all of the zones . I have tried creating local username of the VCSe to check if the authentication is passing through but this is also failing .

What else can I check for troubleshooting?

8 REPLIES 8
oracat777
Beginner

hello Peter,

is there any error logs in VCSe, VCSc and TMS?

Yu.

I have the following logs for a call that I was placing and I can see the call as being rejected


2013-06-25T13:30:41+10:00tvcs: Event="Call Rejected"  Service="SIP" Src-ip="199.19.190.26"  Src-port="5060" Src-alias-type="SIP" Src-alias="sip:peteranders74@jabber.com"  Dst-alias-type="SIP" Dst-alias="sip:62252@103.9.63.213"  Call-serial-number="9c90aeca-dd47-11e2-89b1-0010f325dddc"  Tag="9c90b078-dd47-11e2-a308-0010f325dddc"  Detail="Not Found" Protocol="TCP" Response-code="404" Level="1"  UTCTime="2013-06-25  03:30:41,376"
2013-06-25T13:30:41+10:00tvcs: Event="Search Completed"  Reason="Not Found" Service="SIP" Src-alias-type="SIP" Src-alias="peteranders74@jabber.com"  Dst-alias-type="SIP" Dst-alias="sip:62252@103.9.63.213"  Call-serial-number="9c90aeca-dd47-11e2-89b1-0010f325dddc"  Tag="9c90b078-dd47-11e2-a308-0010f325dddc"  Detail="found:false,  searchtype:INVITE, Info:Policy Response" Level="1"  UTCTime="2013-06-25  03:30:41,376"
2013-06-25T13:30:41+10:00tvcs: Event="Call Attempted"  Service="SIP" Src-ip="199.19.190.26"  Src-port="5060" Src-alias-type="SIP" Src-alias="sip:peteranders74@jabber.com"  Dst-alias-type="SIP" Dst-alias="sip:62252@103.9.63.213"  Call-serial-number="9c90aeca-dd47-11e2-89b1-0010f325dddc"  Tag="9c90b078-dd47-11e2-a308-0010f325dddc"  Protocol="TCP" Auth="NO"  Level="1" UTCTime="2013-06-25  03:30:41,371"
2013-06-25T13:30:41+10:00tvcs: Event="Search Attempted"  Service="SIP" Src-alias-type="SIP" Src-alias="peteranders74@jabber.com"  Dst-alias-type="SIP" Dst-alias="sip:62252@103.9.63.213"  Call-serial-number="9c90aeca-dd47-11e2-89b1-0010f325dddc"  Tag="9c90b078-dd47-11e2-a308-0010f325dddc"  Detail

can you please check the "Search history" logs to find why 62252@103.9.63.213 can not be reached?

or you may make SRV record for your public domian name, then you can try to call 62252@domain-name.

thanks.

I am creating the SRV records but here is the log for why the call did not complete

  • Search (46)
    • State: Completed
    • Found: False
    • Reason: Not Found
    • Info: Policy Response
    • Type: SIP (INVITE)
    • CallSerial Number: 9c90aeca-dd47-11e2-89b1-0010f325dddc
    • Tag: 9c90b078-dd47-11e2-a308-0010f325dddc
    • Source (1)
      • Authenticated: False
      • Zone (1)
        • Name: DefaultZone
        • Type: Default
      • Path (1)
        • Hop (1)
          • Address: 199.19.190.26:5060
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: sip:62252@103.9.63.213
    • StartTime: 2013-06-25 13:30:41
    • Duration: 0.01
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 62252@103.9.63.213
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 62252@103.9.63.213
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 62252@103.9.63.213
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: LocalZoneMatch
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2013-06-25 13:30:41
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 103.9.63.213:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 62252@103.9.63.213
              • Zone (2)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2013-06-25 13:30:41
                • Duration: 0.01
                • Gatekeeper (1)
                  • Address: 103.9.63.213:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 62252@103.9.63.213

can you try to transform the called party from 62252@103.9.63.213 to 62252 or something your VCS expressway can recognize or  route it to VCS control?

thanks.

Yu.

I am getting the transform to work correctly in the calls however it is still failing when hitting the Local Zone ( See Log above )

I am also epxeriencing the issues when I call from the iPad the call hits the expressway no problems but when I call from a Windows client it is not presenting to the expressway

Hi,

Peter opened the Case with Cisco TAC and we were able to fix the issue by changing the config in TMS and changing the search rules on the VCS.

There were some issues with firewall port openings as well and after opening those ports the calls are connected fine without any problem.

Rgds

Alok

Martin Koch
Advocate

It looks like multiple problems, one regards a free-jabber-video call to some address inside

The question would be what is 103.9.63.213 (guess your vcse) and what is 62252 and where is that registered (vcs-c or -e).

Especially if you want to use sip I recommend that you properly introduce domain based uri dialing

including SRV records for your domain.

Just using ips can be a bit confusing regards search rules, transforms, ip vs alias matching, ...

In this case you can see in the log that the vcs sends out a 404 which is simply not found.

A good start is the documentation for the VCS like

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

Your own Jabber provisioning is dependent that the base setup is correct, there are

many ways how to deploy it, including many parameters, ...

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tmspe/install_guide/Cisco_TMSPE_Deployment_Guide_1-0_with_14-1.pdf

Please check out other tms and vcs guides as well.

I would recommend that you reach out to a Cisco partner or consultant to review your setup and

configuration, it looks that you need some general review of your deployment, this can also be

helpful for you as some kind of look over the shoulder training /  qna session  :-)

Please remember to rate helpful responses and identify

Create
Recognize Your Peers
Content for Community-Ad