[AsteriskBrasil] Problema X-lite com IP Virtual
Weder Prado
weder.prado em gmail.com
Segunda Junho 1 05:00:22 BRT 2009
Olá pessoal,
Estou fazendo laboratórios de Asterisk com alta disponibilidade, por
enquanto tenho um heartbeat fazendo a parte de failover, onde tenho um ip
virtual, no caso 172.33.16.220, onde esse ip aponta para o host que está com
o asterisk ativo. O ambiente está certinho, asterisk 1.6 + FreePBX 2.5.1,
com o Zoiper eu consigo registrar no IP virtual normalmente, agora com o
X-lite não funciona, segue o sip debug:
REGISTER sip:172.33.16.220 SIP/2.0
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:2589 em 172.33.33.150:38595;rinstance=b73d4d015d9d419d>
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>>
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 0
<------------->
--- (12 headers 0 lines) ---
Sending to 172.33.33.150 : 38595 (NAT)
<--- Transmitting (NAT) to 172.33.33.150:38595 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;received=172.33.33.150;rport=38595
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=as504997ac
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Server: Asterisk PBX 1.6.1.0-rc4
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="07312465"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog
'YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.' in 32000 ms (Method:
REGISTER)
voipfailover*CLI>
<--- SIP read from UDP://172.33.33.150:38595 --->
REGISTER sip:172.33.16.220 SIP/2.0
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:2589 em 172.33.33.150:38595;rinstance=b73d4d015d9d419d>
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>>
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 0
<------------->
--- (12 headers 0 lines) ---
Sending to 172.33.33.150 : 38595 (NAT)
<--- Transmitting (NAT) to 172.33.33.150:38595 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;received=172.33.33.150;rport=38595
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=as504997ac
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Server: Asterisk PBX 1.6.1.0-rc4
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="07312465"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog
'YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.' in 32000 ms (Method:
REGISTER)
voipfailover*CLI>
<--- SIP read from UDP://172.33.33.150:38595 --->
REGISTER sip:172.33.16.220 SIP/2.0
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:2589 em 172.33.33.150:38595;rinstance=b73d4d015d9d419d>
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>>
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 0
<------------->
--- (12 headers 0 lines) ---
Sending to 172.33.33.150 : 38595 (NAT)
<--- Transmitting (NAT) to 172.33.33.150:38595 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;received=172.33.33.150;rport=38595
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=as504997ac
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Server: Asterisk PBX 1.6.1.0-rc4
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="07312465"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog
'YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.' in 32000 ms (Method:
REGISTER)
voipfailover*CLI>
<--- SIP read from UDP://172.33.33.150:38595 --->
REGISTER sip:172.33.16.220 SIP/2.0
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:2589 em 172.33.33.150:38595;rinstance=b73d4d015d9d419d>
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>>
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE,
INFO
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 0
<------------->
--- (12 headers 0 lines) ---
Sending to 172.33.33.150 : 38595 (NAT)
<--- Transmitting (NAT) to 172.33.33.150:38595 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.33.33.150:38595
;branch=z9hG4bK-d8754z-43603b4ff51a741d-1---d8754z-;received=172.33.33.150;rport=38595
From: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=2e024a16
To: "Teste Failover"<sip:2589 em 172.33.16.220 <sip%3A2589 em 172.33.16.220>
>;tag=as504997ac
Call-ID: YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.
CSeq: 1 REGISTER
Server: Asterisk PBX 1.6.1.0-rc4
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="07312465"
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog
'YTk2NmFkZjZkYTA3MWE4NTg3ZjQ4ODIwMDQzMjM1OTE.' in 32000 ms (Method:
REGISTER)
voipfailover*CLI>
Os dados cadastrados no x-lite estão corretos, tanto que se tento registrar
direto no host eu consigo, alguma dica do que pode ser?
Abs,
Weder
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: http://listas.asteriskbrasil.org/pipermail/asteriskbrasil/attachments/20090601/924830d1/attachment.htm
Mais detalhes sobre a lista de discussão AsteriskBrasil