•   
  • 1
  • 17
  • 18
  • 19(current)
  • 20
  • 21
  • 43
  •   
Help us solving the AirPlay issue when using iOS7 devices
(2014-01-24, 22:36)ermax Wrote: Basically I am sending out an ad just like the one XBMC sends the only difference is I am using a different name than the one set in System>Services>General>Device Name. After I send that ad I wait 5secs and then launch XBMC and that is all there is to it.

On windows Bonjour comes with a command line utility called dns-sd. I simply run this command:
Code:
dns-sd -R "-Noel XBMC" _airplay local 36667 "deviceid=FF:FF:FF:FF:FF:FF" "features=0x77" "model=Xbmc,1" "srcvers=101.28"

Just change the MAC and name to match your setup. Be sure to change the name a little so it isn't an exact match. I just prefix the name with a hyphen. Not sure what the equivalent to dns-sd is in Linux though.

Maybe this?:
http://manpages.ubuntu.com/manpages/rari...ish.1.html
Code:
avahi-publish -s "-Noel XBMC" _airplay 36667 "deviceid=FF:FF:FF:FF:FF:FF" "features=0x77" "model=Xbmc,1" "srcvers=101.28"

it requires avahi-utils on ubunto, but no bother

command line seems to need altering to:
PHP Code:
avahi-publish -"MyXBMC2" _airplay._tcp 36667 "deviceid=b8:27:eb:b4:7c:8c" "features=0x77" "model=Xbmc,1" "srcvers=101.28" 

After numerous attempts to try and break this, I can confirm that this rock steady, numerous wifi restarts.

I am actually using raspbmc DEC build, so none of the testbuilds.

its a hack...but hell it seems to work Smile Good work guys
Reply
(2014-01-24, 22:36)ermax Wrote: Basically I am sending out an ad just like the one XBMC sends the only difference is I am using a different name than the one set in System>Services>General>Device Name. After I send that ad I wait 5secs and then launch XBMC and that is all there is to it.

On windows Bonjour comes with a command line utility called dns-sd. I simply run this command:
Code:
dns-sd -R "-Noel XBMC" _airplay local 36667 "deviceid=FF:FF:FF:FF:FF:FF" "features=0x77" "model=Xbmc,1" "srcvers=101.28"

Just change the MAC and name to match your setup. Be sure to change the name a little so it isn't an exact match. I just prefix the name with a hyphen. Not sure what the equivalent to dns-sd is in Linux though.

It works for me as well (XBMC 13 Alpha12 20140124)
I have restarted the Airport Extreme as well as my iPhone 5. It keeps showing the monitor icon.
Reply
I too have managed to get video/pictures working using the following strings:


Code:
avahi-publish -s "MyXBMC2" _airplay._tcp 36667 "deviceid=<MACADDRESS>" "features=0x1000009FF" "model=Xbmc,1" "srcvers=101.28"

Code:
avahi-publish -s "<MACADDRESS>@MyXBMC2" _raop._tcp 36666 "txtvers=1" "cn=0,1" "ch=2" "ek=1" "et=0,1" "sv=false" "tp=UDP" "sm=false" "ss=16" "sr=44100" "pw=false" "vn=3" "da=true" "vs=130.14" "md=0,1,2" "am=Xbmc,1"

It originally didnt work, and I noticed that in the bonjour messages being sent there was no IPv6 address. I enabled IPv6 and rebooted and hey presto!

I don't have any audio so I need to work on that next!
Reply
Yeh, upon testing I seem to have the same issue, Video works fine, however no audio
Reply
Hi all,

Using xbmc nightly with OpenELEC 4.0 nightly Gotham builds and ipad2/iphone5s. I was successfully being able to reproduce switching from unworking (speaker only) to working (monitor mode) and logged everything with enableairtunesdebuglog.

The trick that worked every time for me was:
0. initial state: xbmc airplay on, iDevice sees only speaker in control center, playing music not possible, no airplay device in pictures
1. disable wireless on iDevice
2. enable wireless
3. disable AirPlay on xbmc
4. enable AirPlay on xbmc
5. final state: airplay visible as monitor, can connect and play (not videos on iphone5s tough, more details below)

Software used: - OpenELEC-Generic.x86_64-devel-20140124114114-r17131-g0f6c504.img
XBMC (13.0-ALPHA12 Git:910ac62). Platform: x86 Linux 64-bit
Using Release XBMC x64 build, compiled Jan 24 2014 by GCC 4.7.3 for x86 Linux 64-bit 3.13.0
Running on Linux 64-bit (OpenELEC (official) - Version: devel-20140124114114-r17131-g0f6c504, 3.13.0 x86_64)

Hardware used: Intel NUC D34010WYK, Synology NAS DS713+ SMB/NFS and DSM 4.3, NAD A/V T755, Panasonic TX-P42G30E

Additional notes:
1. I booted off clean live version of openelec out from usb just to test it clean, and it's completely the same as booting from ssd with my plugins.
2. at one point I suspected my wifi broadband router kills xbmc zeroconf. tried using both dhcp/manual network address for xbmc, but it did not make any difference. can reproduce this in both scenarios

Strange findings:
1. if I disable airplay in xbmc - iDevices still see xbmc device in control center / airplay. it completely goes away on iDevice only when I disable wifi, but when I reenable wifi, iDevice still sees xbmc, although airplay on xbmc is still off
2. if i disable/enable airplay on xbmc, idevice sees that and for a second disables/enables airplay icon in control center (after that everything airplay works).
3. after I disable airplay in xbmc, and try to connect to it via iDevice, i was able to crash xbmc couple of times

Hope this will help. Can provide additional details if needed, plx pm-me, really want to get this working. Smile

Initial state:
1. iPad2, iPhone5s
2. 7.0.4
3. yes
4. no
5. no
6. no - xbmc does not show up at all in pictures / airplay menu
7. no

After "disabling/enabling":

1. iPad2
2. 7.0.4
3. no
4. yes
5. yes
6. yes, but slideshow option does not work
7. yes

1. iPhone5s
2. 7.0.4
3. no
4. yes
5. no
6. yes, but slideshow option does not work
7. yes


Here is a snippet of xbmc.log in NON WORKING state (sorry for breaking forum no idea how to limit width).

(192.168.1.23 - xbmc, 192.168.1.22 - iphone5s)

Code:
12:14:25 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:14:25 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:14:25 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:14:25 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:25 T:140225430935296   DEBUG: AIRTUNES: Got challenge: arH9wkjlKkGy+VVse9C+EQ==
12:14:25 T:140225430935296   DEBUG: AIRTUNES: Got response: wzoH64EgVn3TqRrRI+C2f1tHLv93AWFGMM+0gYE2xZTWJlUbh40Hv16YZgztERtPLmUSGElw1rprrwVqnJl3lpEa1cjifbjBVkyKuUCk
12:14:25 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:14:25 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:25 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:14:36 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:14:36 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:14:36 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:14:36 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:36 T:140225430935296   DEBUG: AIRTUNES: Got challenge: Ejelaql+w/WReYs+bUsDMA==
12:14:36 T:140225430935296   DEBUG: AIRTUNES: Got response: lv+5AuQDHDib5j+adQq/eOKcxPLLfBBYmGwu5Mm61r2dtgG/7+Dws3Td37IHxWZZbgOSMlvPBhE1UUsvldVXuxuZQSxgGrAd6Fnrpdjg
12:14:36 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:14:36 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:36 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:14:55 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:14:55 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:14:55 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:14:55 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:55 T:140225430935296   DEBUG: AIRTUNES: Got challenge: SSlA3FCU7mawhPgeJZiZNQ==
12:14:55 T:140225430935296   DEBUG: AIRTUNES: Got response: zDvDjpq/HQJY5k+KZeEv1FlHzTca5a1TKhC25yZdd9a67CgGAujNaIZeOA3EqpSGrvVFkeKvgItq64Kz6Z2kFfUC4ASMQv8mZibK2/Id
12:14:55 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:14:55 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:55 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:14:59 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:14:59 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:14:59 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:14:59 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:59 T:140225430935296   DEBUG: AIRTUNES: Got challenge: qZbaK1ZWld0zQHUro0pPmQ==
12:14:59 T:140225430935296   DEBUG: AIRTUNES: Got response: bhuKDeYUhY52FEwSlKf0SaAwdHicRNwofGqrNC+5XRvBeMvCNkvYfiFvNIw/eV024S7pYzd+DLwRnWfVahdzvMMnBlbGKJ4vtNFQCO9z
12:14:59 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:14:59 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:14:59 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:15:15 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:15:15 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:15:15 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:15:15 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:15 T:140225430935296   DEBUG: AIRTUNES: Got challenge: Qk0d6PXQJRXTsXtNJ2oiOA==
12:15:15 T:140225430935296   DEBUG: AIRTUNES: Got response: JKke5+LD9HiM05LwjQnh3NJyZrzzgKyL7bC9ydU1e4cHwprldkY6F54Aeyk27NyQHJv35+/o1CgrqYj+7JjWzfJ/xtNkMSZzoRO/H2hp
12:15:15 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:15:15 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:15 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:15:21 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:15:21 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:15:21 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:15:21 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:21 T:140225430935296   DEBUG: AIRTUNES: Got challenge: GpG56cWhhdWhxv3avjjf6g==
12:15:21 T:140225430935296   DEBUG: AIRTUNES: Got response: Q0qkb/mMRyqnoktYqcCHuQg8KkIK0hbW0toPVBpBHE5fe0Rb2gFw/pbcinNAFdF0409BIBBqElp57b0UDzZNRcH0oYvPrZOfLO395KNR
12:15:21 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:15:21 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:21 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:15:26 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:15:26 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:15:26 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:15:26 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:26 T:140225430935296   DEBUG: AIRTUNES: Got challenge: /AlMQmhwgA9h9cx5sBiyDw==
12:15:26 T:140225430935296   DEBUG: AIRTUNES: Got response: jZrgtCTZuurjWAWX1tsXUdFEBa3HYr6yV1S9pCmcNo8Ah//er+jqSHZvNCwoxA8UqQQtv+X0zGILB8g/bzE57gBI2VhIo/wXotqWsYqt
12:15:26 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:15:26 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:26 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:15:31 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:15:31 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:15:31 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:15:31 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:31 T:140225430935296   DEBUG: AIRTUNES: Got challenge: 9ryX2dC62eA8jpeYdMLcHw==
12:15:31 T:140225430935296   DEBUG: AIRTUNES: Got response: IJcQI9Z8e8FG6Yx5JFM/Px6BcsAby8psGZJ36NLz3Yy0tJLigYyfUkT5kuK5TwFzOYs+Cxovb18oQjoPctO8yoKR3Ae5ZefvkRJ0gJKf
12:15:31 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:15:31 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:31 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12
12:15:43 T:140225430935296    INFO: AIRTUNES: Accepted IPv4 client on socket 12
12:15:43 T:140225430935296    INFO: AIRTUNES: Local: 192.168.1.23
12:15:43 T:140225430935296    INFO: AIRTUNES: Remote: 192.168.1.22
12:15:43 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:43 T:140225430935296   DEBUG: AIRTUNES: Got challenge: 95LHClo1MolfSNkahafyHA==
12:15:43 T:140225430935296   DEBUG: AIRTUNES: Got response: uWNlmSVAcvmwy8VDTelBiE7oD0r14P4M+/6y9lownWqiMITiXDLJhxfxZfk7rEIOEVK9BO239ONAP4OxJDISa07649jRRQ0UqjzfEVRj
12:15:43 T:140225430935296   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
12:15:43 T:140225430935296   DEBUG: AIRTUNES: Receiving on socket 12
12:15:43 T:140225430935296    INFO: AIRTUNES: Connection closed for socket 12


and this is snippet of WORKING xbmc.log
Code:
13:05:19 T:139772035057408    INFO: AIRTUNES: Accepted IPv4 client on socket 60
13:05:19 T:139772035057408    INFO: AIRTUNES: Local: 192.168.1.23
13:05:19 T:139772035057408    INFO: AIRTUNES: Remote: 192.168.1.22
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Receiving on socket 60
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Got challenge: oQGMm7TInHqt95iaNteZQw==
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Got response: ihgJR+CBlNE6m9P1Vl1SQ/giw+YBViRBSoNRRKRrhUgpZ2qPIGS746285rqS8jueSisS5iwN9sg+79/+icDH8+VOGbLRRENNn174CGQb
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Handled request OPTIONS with URL *
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Receiving on socket 60
13:05:19 T:139772035057408   DEBUG: AIRTUNES: connection: IN IP4 192.168.1.22
13:05:19 T:139772035057408   DEBUG: AIRTUNES: rtpmap: 96 AppleLossless
13:05:19 T:139772035057408   DEBUG: AIRTUNES: fmtp: 96 352 0 16 40 10 14 2 255 0 0 44100
13:05:19 T:139772035057408   DEBUG: AIRTUNES: rsaaeskey: HlaeoZ9NN62PGHikxJrz6M9qd0XdWnGzP6tOxtRlnwRdjsYuWSJiQGHkU4TkNTUD9Pi86ripb1wNy0n05rgVTFbMKTGJGVktI5JQg5TUiBK
13:05:19 T:139772035057408   DEBUG: AIRTUNES: aesiv: AdufuRsg5qejxJtiwf9Wlg==
13:05:19 T:139772035057408   DEBUG: AIRTUNES: aeskeylen: 16
13:05:19 T:139772035057408   DEBUG: AIRTUNES: aesivlen: 16
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Handled request ANNOUNCE with URL rtsp://192.168.1.23/15337007272073776762
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Receiving on socket 60
13:05:19 T:139772035057408    INFO: AIRTUNES: Transport: RTP/AVP/UDP;unicast;mode=record;timing_port=51458;x-events;control_port=49599
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Found remote timing port: 51458
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Found remote control port: 49599
13:05:19 T:139772035057408    INFO: AIRTUNES: Responding with RTP/AVP/UDP;unicast;mode=record;timing_port=49955;events;control_port=48254;server_port=50661
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Handled request SETUP with URL rtsp://192.168.1.23/15337007272073776762
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Receiving on socket 60
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Handled request RECORD with URL rtsp://192.168.1.23/15337007272073776762
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Receiving on socket 60
13:05:19 T:139772035057408   DEBUG: AIRTUNES: Handled request SET_PARAMETER with URL rtsp://192.168.1.23/15337007272073776762

Best regards

edited: managed to 'limit' forum width by stripping challenge data.
Reply
OK so further testing on Ubuntu.

This works VERY well for Audio, Video, Pictures, by changing the Model it also now works with PLEX after 2 months of no joy! Smile

You must execute the command below AFTER XBMC appears as an AIRPLAY target (if you place this in your /etc/rc.local I suggest delaying the execution about 15-20 seconds.

This is largely based on the work done by ermax

PHP Code:
avahi-publish -"iXBMC" _airplay._tcp 36667 "deviceid=XX:XX:XX:XX:XX:XX" "features=0x77" "model=AppleTV3,2" "srcvers=101.28" 
Reply
Amazing, this (above post from catkinso) works perfectly for me. I registered here, just to say that.
Reply
The question is, why does this hacky method work even though we are basically sending the same advertisement.
Reply
another question - will it work if xbmc does 2 announcements aswell? Please try testbuid 9 from first post...
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for Kodi: NFS (wiki)
HowTo configure avahi (zeroconf): Avahi_Zeroconf (wiki)
READ THE IOS FAQ!: iOS FAQ (wiki)
Reply
(2014-01-26, 23:58)Memphiz Wrote: another question - will it work if xbmc does 2 announcements aswell? Please try testbuid 9 from first post...

I was a bit dismayed when this build popped up as an audio target first. But after a wifi toggle, it switched to a full target, and everything (music, photos, video) seemed to work from my brief testing. Furthermore, it stayed a full target consistently over something like a dozen further wifi toggles. I wasn't keeping count, but it did at some point eventually switch back once to an audio-only, but went back to full target after another wifi toggle, so this fix seems to work the vast majority of the time.

win32 build, iphone5 7.0.4
Reply
(2014-01-26, 23:58)Memphiz Wrote: another question - will it work if xbmc does 2 announcements aswell? Please try testbuid 9 from first post...

I wrote earlier that it worked for me.

It turns out it only works consistently (for me) if two XBMC sessions are running on two different machines on my network.
I had been testing ermax's dns-sd announcement on my pc while my HTPC was running as well. When I tested this set up on my HTPC, it only worked sometimes. I then turned on my other pc, started XBMC and ermax's method worked again.
Reply
(2014-01-26, 23:58)Memphiz Wrote: another question - will it work if xbmc does 2 announcements aswell? Please try testbuid 9 from first post...

Sorry Memphiz I cannot run your test builds as I am running raspbmc.

Interestingly, there distinctly different behavior between iphone5 & ipad.(7.0.4)

I find Camera video is flaky on the iphone, it tries to stream but seems to screw up somewhere along the way , but perfect on the ipad.

Both work, however the IPAD sees only the iXBMC, wheras iphone see's XBMC

If I can make a request, future airplay XBMC publications should follow model=AppleTV3,2. Some applications such as PLEX look for this.
Reply
Yeah you can request this after you have read the wohle thread and the implications with announcing AppleTV3,2. Alot of users in this thread did alot of testing with different announces. And just suggesting something without understanding the implications doesn't help here.

I know you want to help but... What exactly makes you think that AppleTV3,2 is the way to go or that it even fixes anything (without breaking it for older ios Versions like 6 or 5)?
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for Kodi: NFS (wiki)
HowTo configure avahi (zeroconf): Avahi_Zeroconf (wiki)
READ THE IOS FAQ!: iOS FAQ (wiki)
Reply
I haven't had a chance to push any media (due to family using the TV), but I can share that it's been about 12 hours and the "Full Target" TV icon is still shown on my iPhone 5, running iOS 7.0.4.
XBMC running on Windows 8.1, 64 bit.
Reply
I gave this fix a quick try this morning with my dev ios device, seems to work great.

Testbuild 9, Win32

1. Iphone 5s
2. 7.1 Beta 4
3. Shows as Monitor
4. Yep
5. Youtube works
6. Yes, haven't tried slideshow though
7. music works
Reply
  •   
  • 1
  • 17
  • 18
  • 19(current)
  • 20
  • 21
  • 43
  •   



Logout Mark Read Team Forum Stats Members Help
Help us solving the AirPlay issue when using iOS7 devices7
This forum uses Lukasz Tkacz MyBB addons.