Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
38 Views

hello,can help me to solve the sip-portal start problem

while i set on the console for sip info,and i had apply it。then when i /start-all.sh the owt,my sip-portal have no  fail link to agent

 

 The attachment is the log, can evenry one help me to solve the problem? thanks very much!

 

2019-09-06 22:26:46.224  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672, login: 'admin' }
2019-09-06 22:26:46.306  - INFO: SipPortal - sip-portal up!
2019-09-06 22:26:46.418  - INFO: SipPortal - initSipRooms ok
2019-09-06 22:26:51.542  - WARN: SipPortal - Allocate sip Erizo fail:  Failed to get sip agent:
2019-09-06 22:26:51.543  - INFO: SipPortal - Try to allocate after 5 s.
2019-09-06 22:26:59.405  - INFO: SipErizoHelper - Successully schedule sip node  sip-ee42b0a4e8efeda8c96f@192.168.1.158_0  for  { room: '5d722e7d78f2be082bab9eb6',
  task: '5d722e7d78f2be082bab9eb6' }

 

 

 

while i open the log debug  the info like next 

 

 

2019-09-06 23:25:24.064  - DEBUG: AmqpClient - Connecting to rabbitMQ server: { host: 'localhost', port: 5672 }
2019-09-06 23:25:24.370  - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672, login: 'admin' }
2019-09-06 23:25:24.415  - DEBUG: AmqpClient - Exchange owtRpc is open
2019-09-06 23:25:24.428  - DEBUG: AmqpClient - Reply queue for rpc client amq.gen-vovkIuZd9ANY5E4iPaTOUw is open
2019-09-06 23:25:24.438  - DEBUG: AmqpClient - Exchange owtRpc is open
2019-09-06 23:25:24.447  - DEBUG: AmqpClient - Request queue for rpc server sip-portal is open
2019-09-06 23:25:24.450  - INFO: SipPortal - sip-portal up!
2019-09-06 23:25:24.450  - DEBUG: SipPortal - Start to get SIP rooms
2019-09-06 23:25:24.547  - WARN: SipPortal - --->0Get sip rooms from: [ { roomId: '5d722e7d78f2be082bab9eb6',
    sip: { sipServer: '192.168.1.158',
       username: '1005',
       password: 'c38cf78fad' } } ]
2019-09-06 23:25:24.548  - DEBUG: SipPortal - --->2SIP rooms [ { roomId: '5d722e7d78f2be082bab9eb6',
    sip: { sipServer: '192.168.1.158',
       username: '1005',
       password: 'c38cf78fad' } } ]
2019-09-06 23:25:24.549  - DEBUG: SipPortal - ----------��createSipConnectivity Sip info �� 5d722e7d78f2be082bab9eb6 192.168.1.158 1005 12345
2019-09-06 23:25:24.549  - INFO: SipPortal - ----3initSipRooms ok
2019-09-06 23:25:24.557  - DEBUG: AmqpClient - remoteCall, corrID: 0 to: owt-cluster method: schedule
2019-09-06 23:25:24.565  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 0,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }

2019-09-06 23:25:24.565  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:24.566  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:24.766  - DEBUG: AmqpClient - remoteCall, corrID: 1 to: owt-cluster method: schedule
2019-09-06 23:25:24.770  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 1,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:24.770  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:24.770  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:24.971  - DEBUG: AmqpClient - remoteCall, corrID: 2 to: owt-cluster method: schedule
2019-09-06 23:25:24.973  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 2,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:24.973  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:24.973  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:25.174  - DEBUG: AmqpClient - remoteCall, corrID: 3 to: owt-cluster method: schedule
2019-09-06 23:25:25.176  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 3,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:25.177  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:25.177  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:25.376  - DEBUG: AmqpClient - remoteCall, corrID: 4 to: owt-cluster method: schedule
2019-09-06 23:25:25.379  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 4,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:25.379  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:25.379  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:25.580  - DEBUG: AmqpClient - remoteCall, corrID: 5 to: owt-cluster method: schedule
2019-09-06 23:25:25.583  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 5,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:25.583  - DEBUG: AmqpClient - Callback callback  -  error
2019-09-06 23:25:25.583  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-06 23:25:25.783  - DEBUG: AmqpClient - remoteCall, corrID: 6 to: owt-cluster method: schedule
2019-09-06 23:25:25.786  - DEBUG: AmqpClient - New message received { data: 'error',
  corrID: 6,
  type: 'callback',
  err: 'Failed in scheduling sip worker, reason: No worker available, all in full load.' }
2019-09-06 23:25:25.786  - DEBUG: AmqpClient - Callback callback  -  error


 

Tags (2)
0 Kudos
4 Replies
Highlighted
Employee
38 Views

Have you checked the logs 'sip-xxxx.log'?

It seems that there're some problems starting sip-agent, so sip-portal cannot find them

0 Kudos
Highlighted
Beginner
38 Views

hello,thanks, the Attachments is my start log,i see the log has a error where start,

sip log sip-portal.stdout  is next ,all the log in attachments 

 

2019-09-10 17:52:53.489  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-10 17:52:53.692  - DEBUG: SipErizoHelper - Failed in scheduling a sip agent, keep trying.
2019-09-10 17:52:53.893  - WARN: SipPortal - Allocate sip Erizo fail:  Failed to get sip agent:
2019-09-10 17:52:53.893  - INFO: SipPortal - Try to allocate after 5 s.
2019-09-10 17:52:58.896  - DEBUG: SipPortal - ----------��createSipConnectivity Sip info �� 5d722e7d78f2be082bab9eb6 192.168.1.158 1005 12345
2019-09-10 17:52:58.907  - INFO: SipErizoHelper - Successully schedule sip node  sip-bd4d5001cf846ac6e624@192.168.1.158_0  for  { room: '5d722e7d78f2be082bab9eb6',
  task: '5d722e7d78f2be082bab9eb6' }
2019-09-10 17:52:58.907  - DEBUG: SipPortal - allocateSipErizo { id: 'sip-bd4d5001cf846ac6e624@192.168.1.158_0',
  addr: '192.168.1.158' }
2019-09-10 17:52:58.913  - DEBUG: SipPortal - Sip node init successfully.
 

0 Kudos
Highlighted
Beginner
38 Views

ARN: SipPortal - Allocate sip Erizo fail:  Failed to get sip agent:
2019-09-10 17:52:53.893  - INFO: SipPortal - Try to allocate after 5 s.

0 Kudos
Highlighted
Beginner
38 Views

when i see the freeswitch ,the owt sip room has register in the freeswitch

0 Kudos