Author Topic: Jabber server. Why Yate treats the message as destined external domain?  (Read 2773 times)

rvr

  • Newbie
  • *
  • Posts: 1
    • View Profile
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

marian

  • Hero Member
  • *****
  • Posts: 513
    • View Profile
The jingle module will add a server item for domain 'mydomain.com' to the jabber server.
This is the reason the jabber server puts the externaldomain parameter in call.route.
There is no check for modules registering server items with the same domain(s) as the jabber server.