Recent Posts

Pages: [1] 2 3 ... 10
1
Yate bugs / Re: XMPP Support (windows)?
« Last post by Crante on February 15, 2019, 09:47:06 AM »
<c2s/jabber:***@***.eu:INFO> Sending to '***.eu' [052E01D8]
-----
<?xml version="1.0" encoding="utf-8"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="***@***.eu" to="***.eu" version="1.0" xml:lang="en">
-----
<c2s/jabber:***@***.eu:INFO> Receiving from '***.eu' [052E01D8]
-----
<?xml version="1.0"?>
-----
<c2s/jabber:***@***.eu:INFO> Receiving from '***.eu' [052E01D8]
-----
<stream:stream version="1.0" xml:lang="en" from="***.eu" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" id="4f04cabe-2a49-43fa-bf8d-479466bbcd54">
-----
<jbclientengine:INFO> Processing event (052E1E10,Start)
<c2s/jabber:***@***.eu:INFO> Receiving from '***.eu' [052E01D8]
-----
<stream:features>
  <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls">
    <required/>
  </starttls>
</stream:features>
-----
<c2s/jabber:***@***.eu:INFO> Sending to '***.eu' [052E01D8]
-----
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
-----
<c2s/jabber:***@***.eu:INFO> Receiving from '***.eu' [052E01D8]
-----
<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
-----
Sniffed 'socket.ssl' time=1550245499.046338
  thread=06C63CBC 'JBStreamProcess'
  data=052E01D8
  retval='(null)'
  param['server'] = 'false'
Returned true 'socket.ssl' delay=0.000000
  thread=06C63CBC 'JBStreamProcess'
  data=052E01D8
  retval='(null)'
  param['server'] = 'false'
  param['handlers'] = 'openssl:100'
<c2s/jabber:***@***.eu:INFO> Sending to '***.eu' [052E01D8]
-----
<?xml version="1.0" encoding="utf-8"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="***@***.eu" to="***.eu" version="1.0" xml:lang="en">
-----
<c2s/jabber:***@***.eu:WARN> Socket read error: Le p�riph�rique ne reconna�t pas la commande.
 (22) [052E01D8]
<jbclientengine:INFO> Processing event (052E2560,Terminated)
Sniffed 'user.notify' time=1550245499.087719
  thread=0284D3D8 'Engine Worker'
  data=00000000
  retval='(null)'
  param['module'] = 'jabberclient'
  param['protocol'] = 'jabber'
  param['account'] = 'jabber:***@***.eu'
  param['line'] = 'jabber:***@***.eu'
  param['username'] = '***'
  param['server'] = '***.eu'
  param['jid'] = '***@***.eu'
  param['registered'] = 'false'
  param['reason'] = 'I/O error'
  param['autorestart'] = 'true'
Returned false 'user.notify' delay=0.009001
  thread=0284D3D8 'Engine Worker'
  data=00000000
  retval='(null)'
  param['module'] = 'jabberclient'
  param['protocol'] = 'jabber'
  param['account'] = 'jabber:***@***.eu'
  param['line'] = 'jabber:***@***.eu'
  param['username'] = '***'
  param['server'] = '***.eu'
  param['jid'] = '***@***.eu'
  param['registered'] = 'false'
  param['reason'] = 'I/O error'
  param['autorestart'] = 'true'
  param['handlers'] = 'client:50,jingle:100'
Unregistered account jabber:***@***.eu reason: I/O error
2
Yate bugs / Re: XMPP Support (windows)?
« Last post by marian on February 14, 2019, 12:37:52 AM »
Please select Settings -> Debug window
Make sure the 'Debug Here' and 'JABBER' options are checked.
Try to connect.
Post here the contents of the output.
3
Yate bugs / Re: h.323
« Last post by net_andy on February 13, 2019, 06:51:31 PM »
Updated Yate from the ports of FreeBSD, when assembling yate, it was updated and assembled with the support of h23plus"
4
Yate bugs / Re: h.323
« Last post by Ioana Stanciu on February 13, 2019, 08:51:37 AM »
Update of what?
If you updated YATE, please post a log of building process.
H323 support is no longer maintained in YATE and it is based of OpenH323. For more details please see:
https://docs.yate.ro/wiki/H323_channel_module
It is noted there that it also works with H323plus, but it's not stable.
5
Yate bugs / h.323
« Last post by net_andy on February 13, 2019, 05:31:49 AM »
After the update, YATE does not work with h.323, it produces just such an error ..

<WARN> /usr/local/lib/yate/h323chan.yate: Undefined symbol "_ZNK7PThread7PrintOnERSo"

FreeBSD12/11 and other...
yate-6.1.0_1
h323plus-1.27.0

6
Yate bugs / XMPP Support (windows)?
« Last post by Crante on February 12, 2019, 05:21:20 PM »
Hello,

I tried to install YATE on Windows in order to use it with my XMPP / Jabber account.
However, it is impossible to configure an account without error (with the same configuration on Pidgin)
if I put port 5222 (client to server)(standard), I have "Failed to connect account" jabber:USERNAME@DOMAIN.tld' Reason : I/O error"
and if I put port 5269 (server to server), I have "Failed to connect account" jabber:USERNAME@DOMAIN.tld' Reason : invalid-namespace"

Server is debian with prosody 0.11, work with all another xmpp client.

maybe protocol jabber: is not good and that we should put xmpp: instead (like for link to xmpp/jabber in web browser)
7
Yate bugs / Re: GPRS issues with Telit modem (error 3101?)
« Last post by nour on February 07, 2019, 04:44:24 AM »
Hello

Do you see the modem registered using (CREG) ? Does it show home network or roaming network?

Thanks,
Nour
8
YateBTS / Re: GPRS issue with Telit modem
« Last post by nour on February 07, 2019, 04:43:37 AM »
Hello

Do you see the modem registered using (CREG) ? Does it show home network or roaming network?

Thanks,
Nour
9
YateBTS / Re: outgoing sip call unauth error
« Last post by h4ckerm4n on February 04, 2019, 05:58:21 AM »
I am using javascript based routing, the code of the external routing is below. Should I do the config you mentioned as well or is it not necessary?

Code: [Select]
function routeExternally(msg) {
   var server = "zzz";
   var called = "xxx";
   var caller = "yyy";
   Engine.output("OUTGOING CALL TO: "+ called +" command: "+"sip/sip:" + called + "@" + server + ":5060");
   Channel.callTo("sip/sip:" + called + "@" + server + ":5060", {"caller":caller});
   Engine.output("Performed!");
}

if(message.called == "1234"){
   routeExternally(message);
}
10
YateBTS / Re: outgoing sip call unauth error
« Last post by Monica Tepelus on February 04, 2019, 02:57:55 AM »
Hi,

I assume you didn't route the call correctly. If you route the call to a gateway to which you previously registered you need to route to: line/$called_nr and add parameter line=name_of_sip_account_from_accfile

https://docs.yate.ro/wiki/Accfile#Example_how_to_define_a_line
Pages: [1] 2 3 ... 10