Difference between revisions of "Talk:Jingle/test"

From JaWiki (Jabber/XMPP wiki)
Jump to: navigation, search
(→‎mzrv jlx: new section)
m (Reverted edits by 49.213.10.192 (talk) to last revision by Binary)
 
Line 402: Line 402:
 
cleaning done.
 
cleaning done.
 
</PRE>
 
</PRE>
−
 
−
== mzrv  jlx ==
 
−
 
−
?Cheap Lebron james Shoes
 
−
 
−
With expensive diamonds being the key concept powering LeBron James?!Y 10th signature shoe we can definitely expect much more styles like this. Let us know if Sapphire X?!Ys happen to be on the short list of must-have make ups for the LBJ10.
 
−
 
−
This isn?!Yt just what I?!Yd call one of the most detailed image possible from the Nike LeBron Times Low, but it?!Ys the best we?!Yve observed so far, and something is better than practically nothing, right? Check out four earlier colorways of the shoe, each featuring the same full-length visible Move Air and Dynamic Flywire because the standard mid-top LeBron X, although the Hyperfuse upper seems to be reworked a little.
 
−
 
−
It's risk-free to assume that just as LeBron James and his personal sneaker collection dominated of late in the shoe game, this upcoming 12 months is going to be work by the Nike LeBron X. Earlier this weekend, that finally struck stores. Yet until now, we'd yet to get a look at the low top version.
 
−
 
−
As the friends at KixAndTheCity have written, the low top version will function Max Air instead of Zoom Air, and can apparently also feature more eye-turning and visible Flywire on the upper.
 
−
 
−
Earlier this year the LeBron 10 produced its first appearance in two brand new colorways following the early start looking we obtained courtesy of LeBron in the Precious metal Medal video game. Today brand new images from the Floridian Away colorway have hit the net. Apt to be Bron's kicks if the Heat sport their throwback tops next time the make-up already offers a lot of guarantee. As opposed to the additional two designs we saw this shoe brings a bit more pazazz that is certain to lure every person in.
 
−
 
−
This particular upcoming color ways for the most recent Nike LeBron 12 looks appropriate for the winter climate. It was first provided a play name of ?!aWind Relax, but it seems like it has right now been dubbed ?!aBlue Diamond?!A. This Lebron james 10 features a two-toned blue higher that gives away from a metallic hue depending on the lighting. It also seems like the particular outsole with the freezing glass images seen in the previous pictures have been scrapped for any solid colored outsole. Mark your own calendars as the Nike LeBron Ten GS ?!aBlue Diamond?!A has a release date upon October Sixth. Stay tuned weight loss info and images surfaces.
 
−
 
−
For the time being, check out the comprehensive images below. How do you experience the change with the outsole? Would it prevent you coppin?!Y this color ways? Feel free to inform us what you think within the comment part below.
 
−
 
−
In accordance with unofficial sources, nowhere Diamond coloring ways of the Nike LeBron X will be released by 50 percent versions !?C with Nike Plus Baseball system ($270) as well as Nike Plus enabled ($200). That?!Ys good news with regard to fans, because the first two !?C Overhead Jewel and also USA Hockey !?C are only obtainable in the more costly $270 version. The particular so called Wind flow Chill LeBron 10 is actually scheduled to be released on October 4th, 2012.
 
−
 
−
lebron south beach, lebron shoes, lebron 8
 
−
 
−
You can maintain your blog by logging in to your Bravenet account. Once you are logged in you can customize the layout, colors, and features. In addition, you can add your own links, edit your profile, add your friends, and change many other options to personalize your blog.
 
−
 
−
Once you begin using your blog, you can view statistics in your members area to see how many people are reading your blog as well as where they come from.
 
−
<a href=http://crossfitkitsilano.com/uploads/Cigarrettes-19.html>http://crossfitkitsilano.com/uploads/Cigarrettes-19.html</a>
 
−
<a href=http://laser-source.com/img/Marlboro-17.html>http://laser-source.com/img/Marlboro-17.html</a>
 
−
<a href=http://alohafido.com/wp-content/img/Cigarettes-3335.html>http://alohafido.com/wp-content/img/Cigarettes-3335.html</a>
 
−
<a href=http://malcolmmotors.com.au/wp-content/img/Cigarettes-2629.html>http://malcolmmotors.com.au/wp-content/img/Cigarettes-2629.html</a>
 
−
<a href=http://www.magninolegnami.it/img/Cigarrettes-166.html>http://www.magninolegnami.it/img/Cigarrettes-166.html</a>
 
−
<a href=http://yakimasunfairparade.com/wp-content/img/Cigarettes-1251.html>http://yakimasunfairparade.com/wp-content/img/Cigarettes-1251.html</a>
 
−
<a href=http://4989.co/wp-content/img/Cigarettes-2160.html>http://4989.co/wp-content/img/Cigarettes-2160.html</a>
 
−
<a href=http://www.keiproe.com/wp-content/img/Marlboro-1687.html>http://www.keiproe.com/wp-content/img/Marlboro-1687.html</a>
 
−
<a href=http://weddingonmull.com/wp-content/css/Marlboro-1525.html>http://weddingonmull.com/wp-content/css/Marlboro-1525.html</a>
 
−
<a href=http://sensisweb.com/wp-content/img/Marlboro-316.html>http://sensisweb.com/wp-content/img/Marlboro-316.html</a>
 
−
 
−
?There is a deep-rooted connection to nature in Celtic bracelets. The designs of the knots and weaves are literal translations from nature into the jewelry. There also is quite a romantic association with Celtic bracelets and the designs used with many who wear them, feeling that there is an idealistic meaning in the specific piece they adorn themselves with. It is well known that the Celts were very passionate and idealistic people which are visually evident in the jewelry designs now used throughout the world.
 
−
 
−
There are so many reasons to buy Celtic bracelets, but the chief reason would have to be the symbolism that they hold. From the weaves, knots and crosses to the materials used, these symbols date back centuries and are strong signs of the Irish heritage they hold.
 
−
 
−
The materials that are commonly used in making Celtic bracelets are silver and leather. These alone match the earthy feel that accompanies the ancient Celtic symbol. As they are durable and will look good with just about any item of clothing, they are a good choice as an accessory.
 
−
 
−
Typically, one material is used to make a bracelet however, on occasion you may find that a silver bracelet has gemstones or other metals included to add to a specific design. Gold and platinum bracelets are also available but are not found as frequently.
 
−
 
−
There are plain, yet well designed bracelets which are well-liked as a way to display your Celtic heritage or even if you are just intrigued with the culture. These are usually made up of a thin piece of metal with a single knot or cross in the centre. Those that have Celtic weaves are closer in look to narrow cuff bracelets. Many people use these as part of their workwear. They are also sometimes worn in more formal settings.
 
−
 
−
With a characteristic width of two to four centimeters of cuff bracelets, there is ample space for weaves and knots and this makes them rather popular. The leather bracelets are usually fully closed to allow for fastening and the metal types are more commonly open at one side so as to easily slip it onto the wrist.
 
−
 
−
Due to a lack of written records of what specific knots, weaves and crosses symbolize, there are no set rules which depict the symbolism or a particular knot, weave or cross however, it is assumed that the popular belief that they represent 'love and brotherhood' is incorrect. The symbolism is said to have more of a general feeling of connections and stability. Different artisans may personalize their own bracelets and attach meaning of their own to them but this will merely be to add uniqueness. If you choose a particular pattern or style of weave, knots or crosses, the reason you chose it is probably because you connect with that specific design and that would be the meaning that the bracelet holds. Hence it becomes very personal and special.
 
−
 
−
<a href=http://zhued.com/wp-content/img/Marlboro-621.html>http://zhued.com/wp-content/img/Marlboro-621.html</a>
 
−
<a href=http://thecausewaytram.co.uk/img/Cigarrettes-1107.html>http://thecausewaytram.co.uk/img/Cigarrettes-1107.html</a>
 
−
<a href=http://dongshengsw.com/wp-content/img/Marlboro-312.html>http://dongshengsw.com/wp-content/img/Marlboro-312.html</a>
 
−
<a href=http://wordpress.chicagohostedvoip.com/wp-content/img/Cigarettes-4446.html>http://wordpress.chicagohostedvoip.com/wp-content/img/Cigarettes-4446.html</a>
 
−
<a href=http://zhued.com/wp-content/css/Marlboro-1617.html>http://zhued.com/wp-content/css/Marlboro-1617.html</a>
 
−
<a href=http://www.studiomedicopicano.it/wp-content/css/Marlboro-1879.html>http://www.studiomedicopicano.it/wp-content/css/Marlboro-1879.html</a>
 
−
<a href=http://www.boyuanbambooflooring.com/img/Marlboro-1555.html>http://www.boyuanbambooflooring.com/img/Marlboro-1555.html</a>
 
−
<a href=http://hongistos.com/wp-content/img/Cigarettes-1160.html>http://hongistos.com/wp-content/img/Cigarettes-1160.html</a>
 
−
<a href=http://visionblog.huaban.com/images/851-cigs.html>http://visionblog.huaban.com/images/851-cigs.html</a>
 
−
<a href=http://everyweight.com/wp-content/css/Marlboro-1412.html>http://everyweight.com/wp-content/css/Marlboro-1412.html</a>
 
−
 
−
Christmas is on its way and its time to think about shopping holidays. What would be a nice Christmas gift, where to get it and how to avoid the Christmas shopping frenzy. Be prepared and do your shopping on time. Waiting until the last week before Christmas will get you stressed out. Choose to shop online and avoid frustration in this cheerful month. Also remember that for a gift to be special it does not have to mean it has to be expensive.
 
−
 
−
Give your loved ones and friends a special gift, a gift that isn't something you can buy on every street corner, a gift that says that you want only the best for them and that you want them kept from harm. This special gift is the Orthodox Prayer Rope which comes in two forms a Prayer Bracelet and a Prayer Necklace.
 
−
 
−
 
−
These popular Prayer Bracelet and Prayer Necklaces are handmade by monks and nuns from Orthodox monastery's, for each knot they tie they pray a prayer. This is what makes these bracelets and necklaces so special and a treasured gift.
 
−
 
−
Even famous movie stars have discovered this holy object and you now see Megan Fox, David Duchovny, Kristen Stewart, Colin Farrell, Brian Austin Green, Matthew Mcconaughey and many other wearing them. Also Orthodox athletes wear these bracelets and necklaces for luck in their match but that is not so strange cause it is a native object for them. Some of these athletes are Anna Kournikova (Tennis), Jelena Jankovic (Tennis), Anna Ivanovic (Tennis), Novak Djokovic (Tennis), Vlade Divac (Basketball retired) and many more.
 
−
 
−
These Orthodox Prayer Bracelets and necklaces also called Chotki or Komboskini come in different colors and sizes. There are also special versions for kids that are made in the same way.
 
−
 
−
Visit our store and blog for more information, just >> click here
 
−
 
−
 
−
 
−
 
 
−
<a href=http://www.jankop.pl/img/Cigarrettes-116.html>http://www.jankop.pl/img/Cigarrettes-116.html</a>
 
−
<a href=http://sivbakerogsteiker.com/wp-content/img/Marlboro-753.html>http://sivbakerogsteiker.com/wp-content/img/Marlboro-753.html</a>
 
−
<a href=http://wallwasherlight.com/images/Marlboro-94.html>http://wallwasherlight.com/images/Marlboro-94.html</a>
 
−
<a href=http://diacoasia.com/wp-content/img/Cigarettes-2550.html>http://diacoasia.com/wp-content/img/Cigarettes-2550.html</a>
 
−
<a href=http://rbinigeria.org/wp-content/img/Cigarettes-1784.html>http://rbinigeria.org/wp-content/img/Cigarettes-1784.html</a>
 
−
<a href=http://udc.com.tr/img/Cigarrettes-1074.html>http://udc.com.tr/img/Cigarrettes-1074.html</a>
 
−
<a href=http://thai-jasmine.com/wp-content/img/Cigarettes-1577.html>http://thai-jasmine.com/wp-content/img/Cigarettes-1577.html</a>
 
−
<a href=http://4989.co/wp-content/img/Marlboro-1744.html>http://4989.co/wp-content/img/Marlboro-1744.html</a>
 
−
<a href=http://www.keiproe.com/wp-content/img/Cigarettes-3059.html>http://www.keiproe.com/wp-content/img/Cigarettes-3059.html</a>
 
−
<a href=http://comfortablepictures.com/wp-content/img/Marlboro-1293.html>http://comfortablepictures.com/wp-content/img/Marlboro-1293.html</a>
 

Latest revision as of 15:46, 18 April 2016

STD out psi media 0.14 (FreeBSD) <> psi media 0.14 (Ubuntu)[edit]

Без STUN, на одной стороне NAT 

send clock is master
state changed
sendbin:
  apprtpsink4
  audioencbin:
    rtpspeexpay5
    speexenc5
    capsfilter9
    audioresample10
    audioconvert10
  volume5
%using speexdsp
Readying AudioIn:[oss,/dev/dsp0.0], refs=1
codec=speex
rate=16000,width=16,channels=1
changing state...
send clock is master
state changed
sendbin:
  apprtpsink5
  audioencbin:
    rtpspeexpay6
    speexenc6
    capsfilter11
    audioresample12
    audioconvert12
  volume6
queue5
bin5:
  capsfilter10
  audioresample11
  audioconvert11
  osssrc15
tee5
speexdsp5
rtppay caps audio: [application/x-rtp, media=(string)audio, clock-rate=(int)16000, encoding-name=(string)SPEEX, encoding-params=(string)1, payload=(int)110, ssrc=(uint)2180135228, clock-base=(uint)3949246459, seqnum-base=(uint)16483]
rtp_started
there are audio payload types
types=1
resolver finished
starting ice for audio
starting transport 192.168.5.11:8010 for component 1
starting transport 192.168.5.11:8011 for component 2
lt_started
lt_started
ice_started
after_ice_started
local candidate ready
flushing local candidates
incoming request: [transport-info]
audio candidates=4
adding 4 remote candidates
4 pairs
1, 192.168.5.11:8010 -> 79.104.207.182:8010
2, 192.168.5.11:8011 -> 79.104.207.182:8011
1, 192.168.5.11:8010 -> 79.104.207.182:8010
2, 192.168.5.11:8011 -> 79.104.207.182:8011
4 after pruning
connectivity check from 192.168.5.11:8010 to 79.104.207.182:8010
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
connectivity check from 192.168.5.11:8010 to 79.104.207.182:8010
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
received validated response
check success
received validated response
check success
received validated response
check success
component 1 already active, not signalling
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
received validated response
check success
component 2 already active, not signalling
audio: average packet size=82, kbps=41
incoming request: [session-terminate]
cleaning up...
Releasing AudioIn:[oss,/dev/dsp0.0], refs=0
cleaning done.

Вторая сторона 

incoming request: [transport-info]
audio candidates=2
adding 2 remote candidates
4 pairs
1, 79.104.207.182:8010 -> 192.168.5.11:8010
2, 79.104.207.182:8011 -> 192.168.5.11:8011
1, 79.104.207.182:8010 -> 192.168.5.11:8010
2, 79.104.207.182:8011 -> 192.168.5.11:8011
4 after pruning
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
using speexdsp
Readying AudioIn:[alsa,default], refs=1
codec=speex
rate=16000,width=16,channels=1
received validated request or indication
received validated request or indication
received validated request or indication
received validated request or indication
changing state...
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
received validated request or indication
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
error/timeout while setting send pipeline to PLAYING
cleaning up...
Releasing AudioIn:[alsa,default], refs=0
cleaning done.
cleaning up...
cleaning done.
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011

STUN[edit]

Все то же самое, но со STUN.

На стороне клиента с NAT прописан stun.iptel.org

Он рабочий. Проверил его 

stun_client stun.xten.com
STUN client version 0.96
Primary: Indepndent Mapping, Port Dependent Filter, preserves ports, no hairpin 
Return value is 0x000017

Но все равно соединение не удается установить. Видно что nat пробрасывает пакеты, но почему-то при этом не подменяет своим адресом (?) 

tcpdump -n -i re0 "udp and (src 79.104.207.182 or dst 79.104.207.182)"

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
13:46:56.043772 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.043997 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.044221 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044429 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044640 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044837 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.045039 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.045254 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.115508 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.116626 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.117875 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.118992 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.120242 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.121741 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.122868 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.124113 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.523891 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
13:46:56.524301 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
13:46:56.525635 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
13:46:56.525872 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
13:46:56.528900 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88
13:46:56.529523 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 64
13:46:56.530504 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88

Два публичных адреса[edit]

tcpdump 

tcpdump -n -i re0 "udp and (src 79.104.207.182 or dst 79.104.207.182)"

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
14:08:39.101659 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:08:39.103168 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:08:39.104579 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:08:39.106651 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:08:39.139657 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:08:39.139901 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:08:39.140115 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:08:39.140340 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:08:39.215642 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:08:39.216875 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:08:39.217895 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:08:39.219112 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:08:39.605483 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:08:39.605877 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:08:39.606958 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:08:39.607698 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:08:39.608949 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:08:39.609203 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:08:39.610389 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:08:39.610786 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64

tcpdump с другой стороны 

14:03:31.431464 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:03:31.431476 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:03:31.431478 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:03:31.472200 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:03:31.472552 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:03:31.473153 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:03:31.473312 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:03:31.473951 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:03:31.474095 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:03:31.474873 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:03:31.475014 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:03:31.475876 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:03:31.476024 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:03:31.476688 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:03:31.477581 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:03:31.478567 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:03:31.478596 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:03:31.478715 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:03:31.478853 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:03:31.505866 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:03:31.507055 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:03:31.508063 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:03:31.883271 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:03:31.886012 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:03:31.886094 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:03:31.886199 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:03:31.886300 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:03:31.954035 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:03:31.956940 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:03:31.959666 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:03:31.960389 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:03:31.961881 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:05:51.342393 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:05:51.344472 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:05:51.344651 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:05:51.344796 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:05:51.447041 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:05:51.447421 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:05:51.448080 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:05:51.448733 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 92
14:05:51.449744 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:05:51.449763 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 92
14:05:51.449922 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 64
14:05:51.450055 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 64
14:05:51.842901 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:05:51.844450 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:05:51.844652 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:05:51.844798 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88
14:05:51.913829 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:05:51.915028 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:05:51.917490 IP 80.78.241.19.8010 > 79.104.207.182.8010: UDP, length 64
14:05:51.919246 IP 80.78.241.19.8011 > 79.104.207.182.8011: UDP, length 64
14:07:50.515056 IP 79.104.207.182.8010 > 80.78.241.19.8010: UDP, length 88
14:07:50.515261 IP 79.104.207.182.8011 > 80.78.241.19.8011: UDP, length 88

XML-log 

<iq type="set" to="b108@jabber.ru/на хате" id="aca1a">
<jingle xmlns="urn:xmpp:jingle:1" initiator="lke@agava.com/Датацентр Коровинский (Агава-6)" action="session-initiate" sid="uBrWEqO3daF9ztOr">
<content creator="initiator" name="A" senders="both">
<description xmlns="urn:xmpp:jingle:apps:rtp:1" media="audio">
<payload-type id="110" name="SPEEX" clockrate="16000"/>
</description>
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1" pwd="FJeKzFYxO03bEvFqkEmJNP" ufrag="Ctgf"/>
</content>
</jingle>
</iq>


<iq from="b108@jabber.ru/на хате" type="result" xml:lang="ru-RU" to="lke@agava.com/Датацентр Коровинский (Агава-6)" id="aca1a"/>


<iq type="set" to="b108@jabber.ru/на хате" id="aca2a">
<jingle xmlns="urn:xmpp:jingle:1" action="transport-info" sid="uBrWEqO3daF9ztOr">
<content creator="initiator" name="A">
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1" pwd="FJeKzFYxO03bEvFqkEmJNP" ufrag="Ctgf">
<candidate generation="0" network="0" port="8010" protocol="udp" component="1" foundation="0" ip="80.78.241.19" priority="2130706431" type="host" id="1G4PEmP4sQ"/>
<candidate generation="0" network="0" port="8011" protocol="udp" component="2" foundation="0" ip="80.78.241.19" priority="2130706430" type="host" id="8Jk2wX3uGC"/>
</transport>
</content>
</jingle>
</iq>


<iq from="b108@jabber.ru/на хате" type="set" xml:lang="ru-RU" to="lke@agava.com/Датацентр Коровинский (Агава-6)" id="ab28a">
<jingle xmlns="urn:xmpp:jingle:1" action="transport-info" sid="uBrWEqO3daF9ztOr">
<content creator="initiator" name="A">
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1" pwd="EtO0MV4TCULVTlOD8Dxg5A" ufrag="hA84">
<candidate generation="0" network="0" port="8010" protocol="udp" component="1" foundation="0" ip="79.104.207.182" priority="2130706431" type="host" id="wE0sLOH2ys"/>
<candidate generation="0" network="0" port="8011" protocol="udp" component="2" foundation="0" ip="79.104.207.182" priority="2130706430" type="host" id="Ng0CknqjhO"/>
<candidate generation="0" network="0" port="8010" protocol="udp" component="1" foundation="0s" rel-addr="79.104.207.182" ip="79.104.207.182" priority="1694498815" type="srflx" id="lxSAoChq6e" rel-port="8010"/>
<candidate generation="0" network="0" port="8011" protocol="udp" component="2" foundation="0s" rel-addr="79.104.207.182" ip="79.104.207.182" priority="1694498814" type="srflx" id="cZsWzM6W4v" rel-port="8011"/>
</transport>
</content>
</jingle>
</iq>


<iq type="result" to="b108@jabber.ru/на хате" id="ab28a"/>


<iq from="b108@jabber.ru/на хате" type="result" xml:lang="ru-RU" to="lke@agava.com/Датацентр Коровинский (Агава-6)" id="aca2a"/>


<iq from="b108@jabber.ru/на хате" type="set" xml:lang="ru-RU" to="lke@agava.com/Датацентр Коровинский (Агава-6)" id="ab29a">
<jingle xmlns="urn:xmpp:jingle:1" action="session-terminate" sid="uBrWEqO3daF9ztOr">
<reason>
<gone/>
</reason>
</jingle>
</iq>


<iq type="result" to="b108@jabber.ru/на хате" id="ab29a"/>

stdout psi 

codec=speex
rate=16000,width=16,channels=1
changing state...
send clock is master
state changed
sendbin:
  apprtpsink14
  audioencbin:
    rtpspeexpay15
    speexenc15
    capsfilter29
    audioresample30
    audioconvert30
  volume15
queue14
bin14:
  capsfilter28
  audioresample29
  audioconvert29
  osssrc33
tee14
speexdsp14
rtppay caps audio: [application/x-rtp, media=(string)audio, clock-rate=(int)16000, encoding-name=(string)SPEEX, encoding-params=(string)1, payload=(int)110, ssrc=(uint)39951517, clock-base=(uint)912861304, seqnum-base=(uint)56030]
rtp_started
there are audio payload types
types=1
resolver finished
starting ice for audio
starting transport 80.78.241.19:8010 for component 1
starting transport 80.78.241.19:8011 for component 2
lt_started
lt_started
ice_started
after_ice_started
local candidate ready
audio: average packet size=82, kbps=41
flushing local candidates
received validated request or indication
user [Ctgf:hA84] is wrong.  it should be [Ctgf:].  skipping
received validated request or indication
user [Ctgf:hA84] is wrong.  it should be [Ctgf:].  skipping
received validated request or indication
user [Ctgf:hA84] is wrong.  it should be [Ctgf:].  skipping
received validated request or indication
user [Ctgf:hA84] is wrong.  it should be [Ctgf:].  skipping
incoming request: [transport-info]
audio candidates=4
adding 4 remote candidates
4 pairs
1, 80.78.241.19:8010 -> 79.104.207.182:8010
2, 80.78.241.19:8011 -> 79.104.207.182:8011
1, 80.78.241.19:8010 -> 79.104.207.182:8010
2, 80.78.241.19:8011 -> 79.104.207.182:8011
4 after pruning
connectivity check from 80.78.241.19:8010 to 79.104.207.182:8010
connectivity check from 80.78.241.19:8011 to 79.104.207.182:8011
connectivity check from 80.78.241.19:8010 to 79.104.207.182:8010
connectivity check from 80.78.241.19:8011 to 79.104.207.182:8011
received validated response
check success
received validated response
check success
component 1 already active, not signalling
received validated response
check success
received validated response
check success
component 2 already active, not signalling
received validated request or indication
received validated request or indication
received validated request or indication
received validated request or indication
incoming request: [session-terminate]
cleaning up...
Releasing AudioIn:[oss,/dev/dsp0.0], refs=0
cleaning done.
Retrieved from "http://jawiki.ru/index.php?title=Talk:Jingle/test&oldid=23045"