SIP traffic for Apple Messages.app screen sharing?


#1

Using a Peplink Balance One with 6.2.1 firmware, two users (one inside on the LAN, one outside on the WAN) are able to use Apple’s Messages.app to communicate text messages, send files & pictures back & forth. However, when we try to initiate a screen sharing connection:

  • one user asks
  • the other user gets the invitation
  • the other user accepts
  • but the session never starts

There is a giant debug log of the connection problems, and I notice that it makes reference to SIP. Here are some example lines. Any ideas what the problem is? We tried the connection with the Peplink’s Network/Misc. Settings/Service Passthrough/SIP : set to both Standard and Compatibility mode but nothing worked.


Date/Time:      2015-08-03 13:52:45 -0700
OS Version:     10.10.4 (Build 14E46)
Report Version: 4

Messages Connection Log:
2015-08-03 13:52:06 -0700: 0x60000038e520: State change from No State to Invited.
2015-08-03 13:52:19 -0700: 0x60000038e520: State change from Invited to Connecting.
2015-08-03 13:52:42 -0700: 0x60000038e520: State change from Connecting to Ended.
2015-08-03 13:52:42 -0700: 0x60000038e520: Error 1008 (Did not receive a response from 0x60000038e520.)

Video Conference Error Report:
49974.312854 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
49976.317908 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
49978.322367 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
49985.330548 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/316)
[SIPConnectIPPort failed]
]
50324.107344 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
50326.112429 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
50328.117172 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
50330.121208 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
50332.126563 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/0)
[SIPConnectIPPort failed]
]
50339.149118 @/SourceCache/VideoConference/VideoConference-473/SIP/SIP.c:2255 type=4 (900A0015/316)
[SIPConnectIPPort failed]
]
... and goes on for 1000 more lines....

Video Conference User Report:
0.000000 @:0 type=5 (00000000/16402)
[Local SIP port]
]
0.000062 @:0 type=5 (00000000/16402)
[Local SIP port]
]
0.000109 @:0 type=5 (00000000/16402)
[Local SIP port]
]
49861.696849 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
49861.696860 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
]
]
49966.302482 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
49966.302488 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
]
]
49966.304002 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1679 type=5 (00000000/0)
[Router]
[FULLCONE]
49966.304006 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1681 type=5 (00000000/0)
[CommNAT Result: 0x00000102
]
]
50225.888446 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
50225.888451 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
]
]
50316.103136 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2085 type=5 (00000000/0)
[Remote Router]
[PORT RESTRICTED]
50316.103140 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VCInitiateConference.m:2087 type=5 (00000000/0)
[Remote CommNAT Result: 0x000000d0
]
]
50316.104866 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1679 type=5 (00000000/0)
[Router]
[FULLCONE]
50316.104869 @/SourceCache/VideoConference/VideoConference-473/Video Conference/VideoConferenceGlobalObjects.m:1681 type=5 (00000000/0)
[CommNAT Result: 0x00000102
]
]


#2

Hi,

May I know LAN user shares screen to WAN user or vice versa?

Based on my understading, Apple Screen Sharing is using TCP 5900. Please find here for more details.


#3
  • The behavior is identical in both directions: if the LAN user initiates, the WAN user gets the invitation, but when they accept, nothing happens. If the WAN user initiates, the LAN user gets the invitation, but when the accept, nothing happens. I can see how this suggests that the SIP communication may be working OK : (because both directions can receive and accept the invitation) but the actual video connection is blocked?
  • On our Balance One, we have nothing happening on port 5900 (no inbound or outbound rules are set.) UpNP and NAT-PMP are both enabled.
  • The WAN user is running on the latest model Apple Airport Extreme.
  • The Messages.app connection doctor reports the WAN side as “Full cone” but the Balance One (LAN) user as “Port Restricted”

Any ideas?


#4

Hi,

No idea at the moment. Not sure what port has been blocked. Please do me favor below.

  1. Login to Balance One > Enter “http://”IP of your device”/cgi-bin/MANGA/support.cgi”.

  2. Navigate to Network Capture > Start. Ensure you perform this in off peak hours.

  3. Test with screen sharing until it failed.

  4. Navigate to Network Capture > Stop > Download.

  5. Download Diagnostic Report (Immediate above of Network Capture).

  6. Open ticket and attach the files generated in step 4 and 5. Do let tech support know the testing source and destination IP you have perform in step 3.

Thank you.


#5

For what it’s worth, I’ve observed the same behavior on a Balance 30 since I upgraded its firmware from 5.4.10 to 6.2.1. NAT-PMP and UPnP are both enabled. I’d be very interested in a solution as well.


#6

Hi Jerry,

Do you mind to perform steps here for us to understand better?


#7

For logistical reasons, it’ll be a little tricky to set up, but I’ll do so as soon as time permits. Thanks.


#8

OK, I’ve captured the requested dump and sent it in attached to a support ticket as requested. Let me know if you need any additional information, and thanks for looking into it.


#9

Hi Jerry,

Sure. Remember to let tech support know the testing source and destination IP as well.

Thank you.