1
Other Yate server issues / Jabber server. Why Yate treats the message as destined external domain?
« on: May 19, 2014, 02:31:09 AM »
Hi,
Why Yate treats the message as destined external domain?
Sniffed 'msg.execute' time=1400485545.743676
thread=0x7294d0 'JBPendingWorker'
data=(nil)
retval='(null)'
param['route_type'] = 'msg'
param['module'] = 'jabber'
param['protocol'] = 'jabber'
param['type'] = 'chat'
param['externaldomain'] = 'true'
param['id'] = '1400485545062-1400485546639'
param['caller'] = 'r@mydomain.com'
param['called'] = 'm@mydomain.com'
param['caller_instance'] = 'IM+'
param['callto'] = 'jabber/m@mydomain.com'
param['body'] = 'Тест'
param['xml'] = '' [0x817630] 'message'
jabberserver.conf:
[general]
domains=mydomain.com
[listener client]
enable=yes
type=c2s
[listener server]
enable=yes
type=s2s
yjinglechan.conf:
[general]
servermode=yes
domains=mydomain.com
Why Yate treats the message as destined external domain?
Sniffed 'msg.execute' time=1400485545.743676
thread=0x7294d0 'JBPendingWorker'
data=(nil)
retval='(null)'
param['route_type'] = 'msg'
param['module'] = 'jabber'
param['protocol'] = 'jabber'
param['type'] = 'chat'
param['externaldomain'] = 'true'
param['id'] = '1400485545062-1400485546639'
param['caller'] = 'r@mydomain.com'
param['called'] = 'm@mydomain.com'
param['caller_instance'] = 'IM+'
param['callto'] = 'jabber/m@mydomain.com'
param['body'] = 'Тест'
param['xml'] = '' [0x817630] 'message'
jabberserver.conf:
[general]
domains=mydomain.com
[listener client]
enable=yes
type=c2s
[listener server]
enable=yes
type=s2s
yjinglechan.conf:
[general]
servermode=yes
domains=mydomain.com