cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
716
Views
0
Helpful
4
Replies
Highlighted

Calls from JabberTablet (via VCS) to Internet Endpoints (SIP) KO!

Hi,

I have  an issue with JabberTablet for Ipad.  

The calls between  JabberTablet and JabberTablet are  OK,

The calls between  JabberTablet and Jabber Video are  OK,

The calls from  JabberTablet  to any public IP is KO!

I use a perfectly working video infrastrastructure:

VCS Control X 7.2

VCS Expressway X 7.2

TMS 13.2.1

All calls to public internet endpoints from Jabber Video are working  perfectly.

When I  look into the VCS Ex for see  what’s wrong,  I found that for every  call from JabberTablet to any public IP  have this format

Public_ip@my_sip_domain.com

In this way my Expressway  doesn’t search the destination endpoint on the public internet.. if I do the same call with the same user from JabberVideo, the call will be connected!

note all calls from Ipad are done from 3G connection with public IP

Does you  have found the same behaviors?  Or does you have any suggestions  ?

Thanks,

Carlo

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Rising star

Calls from JabberTablet (via VCS) to Internet Endpoints (SIP) KO

Carlo,

instead of calling the IP address alone, try inserting a dummy alias in front of the IP address, so that if you want to call 213.80.80.80, enter 'test@213.80.80.80' or something similar on your Jabber iPad client.

- Andreas

View solution in original post

4 REPLIES 4
Highlighted

Re: Calls from JabberTablet (via VCS) to Internet Endpoints (SIP

Here a  search on my vcs ex for a call from user1 (ipad) to a internet  endpoint 213.80.80.80

Search (393)

State: Completed

Found: False

Reason: Proxy Authentication Required

Type: SIP (INVITE)

CallSerial Number: 1dc65064-0ef7-11e2-b124-0010f31f193e

Tag: 1dc65208-0ef7-11e2-99d3-0010f31f193e

Source (1)

Authenticated: False

Aliases (1)

Alias (1)

Type: Url

Origin: Unknown

Value: user1.jabbertablet@my-sip-domain.com

Zone (1)

Name: DefaultZone

Type: Default

Path (1)

Hop (1)

Address: 172.16.52.119:49671

Destination (1)

Alias (1)

Type: Url

Origin: Unknown

Value: sip:213.80.80.80@my-sip-domain.com

StartTime: 2012-10-05 16:15:29

Duration: 0.04

SubSearch (1)

Type: Transforms

Action: Not Transformed

ResultAlias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

SubSearch (1)

Type: Admin Policy

Action: Proxy

ResultAlias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

SubSearch (1)

Type: FindMe

Action: Proxy

ResultAlias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

SubSearch (1)

Type: Search Rules

SearchRule (1)

Name: Local zone – no domain

Zone (1)

Name: LocalZone

Type: Local

Protocol: SIP

Found: False

Reason: Not Found

StartTime: 2012-10-05 16:15:29

Duration: 0

Gatekeeper (1)

Address: 199.99.99.99:0

Alias (1)

Type: H323Id

Origin: Unknown

Value: 213.80.80.80

Zone (2)

Name: LocalZone

Type: Local

Protocol: H323

Found: False

Reason: Not Found

StartTime: 2012-10-05 16:15:29

Duration: 0

Gatekeeper (1)

Address: 199.99.99.99:0

Alias (1)

Type: H323Id

Origin: Unknown

Value: 213.80.80.80

SearchRule (2)

Name: Local zone – full URI

Zone (1)

Name: LocalZone

Type: Local

Protocol: SIP

Found: False

Reason: Not Found

StartTime: 2012-10-05 16:15:29

Duration: 0

Gatekeeper (1)

Address: 199.99.99.99:0

Alias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

Zone (2)

Name: LocalZone

Type: Local

Protocol: H323

Found: False

Reason: Not Found

StartTime: 2012-10-05 16:15:29

Duration: 0

Gatekeeper (1)

Address: 199.99.99.99:0

Alias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

SearchRule (3)

Name: Traversal zone search rule

Zone (1)

Name: TraversalZone

Type: TraversalServer

Protocol: SIP

Found: False

Reason: Proxy Authentication Required

StartTime: 2012-10-05 16:15:29

Duration: 0.01

Gatekeeper (1)

Address: 217.19.158.98:31159

Alias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

Zone (2)

Name: TraversalZone

Type: TraversalServer

Protocol: H323

Found: False

Reason: Not registered - Destination not found

StartTime: 2012-10-05 16:15:29

Duration: 0.01

Gatekeeper (1)

Address: 217.19.158.98:49904

Alias (1)

Type: Url

Origin: Unknown

Value: 213.80.80.80@my-sip-domain.com

Highlighted
Rising star

Calls from JabberTablet (via VCS) to Internet Endpoints (SIP) KO

Carlo,

instead of calling the IP address alone, try inserting a dummy alias in front of the IP address, so that if you want to call 213.80.80.80, enter 'test@213.80.80.80' or something similar on your Jabber iPad client.

- Andreas

View solution in original post

Highlighted

Calls from JabberTablet (via VCS) to Internet Endpoints (SIP) KO

Hi Andreas, with

test@213.80.80.80 work fine.

but how isn't possible to call only the public ip ??

thanks,

Carlo

Highlighted
Rising star

Calls from JabberTablet (via VCS) to Internet Endpoints (SIP) KO

Carlo,

this simply means that the client behavior when calling IP addresses has been implemented slightly different on the Jabber iPad client compared to the Jabber Video client for Windows and Mac.

- Andreas

CreatePlease to create content
Content for Community-Ad

Cisco COVID-19 Survey