Entao fiz os testes agora pelo 3g e funcionou, mas de manha pela wirelles de um cliente nao.
Em 13 de agosto de 2013 12:20, Fernando Trilha <ftri...@gmail.com> escreveu: > no server asterisk não, to esperando o pessoal do firewall me retornar. > > > Em 13 de agosto de 2013 11:40, Jefferson B. Limeira < > j...@internexxus.com.br> escreveu: > > ** >> >> Esses parecem estar certos, mas são todos da interface interna, ou seja, >> estariam certos mesmo... o problema é na outra interface. >> >> E o lsmod, retornou alguma coisa? >> >> Em 2013-08-13 11:15, Fernando Trilha escreveu: >> >> Este ai é o tcpdump, o do firewall terei de ver com a pessoa que cuida >> dele, ele é baseado em linux. >> >> >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 630 >> ACK sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-97b114f393f60c33-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 ACK >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri="sip:04833421234@200.193.70.69:5070 >> ;transport=UDP",response="92a9dcb0400142f6745fea5d142bd419",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:33.051106 IP (tos 0x0, ttl 64, id 6743, offset 0, flags [none], >> proto UDP (17), length 897) >> 192.168.0.101.5070 > 179.252.225.2.5060: SIP, length: 869 >> SIP/2.0 200 OK >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-054d56ba92c5b7a5-1---d8754z-;received=179.252.225.2;rport=5060 >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> To: <sip:04833421234@200.193.70.69:5070 >> >;transport=UDP>;tag=as45a78870 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 INVITE >> Server: Asterisk PBX 1.8.23.0 >> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, >> NOTIFY, INFO, PUBLISH >> Supported: replaces, timer >> Session-Expires: 1800;refresher=uas >> Contact: <sip:04833421234@200.193.70.69:5070> >> Content-Type: application/sdp >> Require: timer >> Content-Length: 228 >> >> v=0 >> o=root 398579285 398579286 IN IP4 200.193.70.69 >> s=Asterisk PBX 1.8.23.0 >> c=IN IP4 200.193.70.69 >> t=0 0 >> m=audio 12514 RTP/AVP 0 8 3 >> a=rtpmap:0 PCMU/8000 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:3 GSM/8000 >> a=ptime:20 >> a=sendrecv >> >> 11:13:33.257404 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 658) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 630 >> ACK sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-97b114f393f60c33-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 ACK >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri="sip:04833421234@200.193.70.69:5070 >> ;transport=UDP",response="92a9dcb0400142f6745fea5d142bd419",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:36.376701 IP (tos 0x0, ttl 64, id 6744, offset 0, flags [none], >> proto UDP (17), length 897) >> 192.168.0.101.5070 > 179.252.225.2.5060: SIP, length: 869 >> SIP/2.0 200 OK >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-054d56ba92c5b7a5-1---d8754z-;received=179.252.225.2;rport=5060 >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> To: <sip:04833421234@200.193.70.69:5070 >> >;transport=UDP>;tag=as45a78870 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 INVITE >> Server: Asterisk PBX 1.8.23.0 >> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, >> NOTIFY, INFO, PUBLISH >> Supported: replaces, timer >> Session-Expires: 1800;refresher=uas >> Contact: <sip:04833421234@200.193.70.69:5070> >> Content-Type: application/sdp >> Require: timer >> Content-Length: 228 >> >> v=0 >> o=root 398579285 398579286 IN IP4 200.193.70.69 >> s=Asterisk PBX 1.8.23.0 >> c=IN IP4 200.193.70.69 >> t=0 0 >> m=audio 12514 RTP/AVP 0 8 3 >> a=rtpmap:0 PCMU/8000 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:3 GSM/8000 >> a=ptime:20 >> a=sendrecv >> >> 11:13:36.432176 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 658) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 630 >> ACK sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-97b114f393f60c33-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 ACK >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri="sip:04833421234@200.193.70.69:5070 >> ;transport=UDP",response="92a9dcb0400142f6745fea5d142bd419",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:40.377363 IP (tos 0x0, ttl 64, id 6745, offset 0, flags [none], >> proto UDP (17), length 897) >> 192.168.0.101.5070 > 179.252.225.2.5060: SIP, length: 869 >> SIP/2.0 200 OK >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-054d56ba92c5b7a5-1---d8754z-;received=179.252.225.2;rport=5060 >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> To: <sip:04833421234@200.193.70.69:5070 >> >;transport=UDP>;tag=as45a78870 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 INVITE >> Server: Asterisk PBX 1.8.23.0 >> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, >> NOTIFY, INFO, PUBLISH >> Supported: replaces, timer >> Session-Expires: 1800;refresher=uas >> Contact: <sip:04833421234@200.193.70.69:5070> >> Content-Type: application/sdp >> Require: timer >> Content-Length: 228 >> >> v=0 >> o=root 398579285 398579286 IN IP4 200.193.70.69 >> s=Asterisk PBX 1.8.23.0 >> c=IN IP4 200.193.70.69 >> t=0 0 >> m=audio 12514 RTP/AVP 0 8 3 >> a=rtpmap:0 PCMU/8000 >> a=rtpmap:8 PCMA/8000 >> a=rtpmap:3 GSM/8000 >> a=ptime:20 >> a=sendrecv >> >> 11:13:40.422249 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 658) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 630 >> ACK sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-97b114f393f60c33-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 2 ACK >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri="sip:04833421234@200.193.70.69:5070 >> ;transport=UDP",response="92a9dcb0400142f6745fea5d142bd419",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:40.574233 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 644) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 616 >> BYE sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-14cb719dd333c35c-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 3 BYE >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri=" >> sip:04833421234@200.193.70.69:5070 >> ",response="4911bfc1a62265954226f72e9b36d4b1",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:41.069084 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 32) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 4 >> >> >> >> 11:13:41.081575 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 644) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 616 >> BYE sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-14cb719dd333c35c-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 3 BYE >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri=" >> sip:04833421234@200.193.70.69:5070 >> ",response="4911bfc1a62265954226f72e9b36d4b1",algorithm=MD5 >> Content-Length: 0 >> >> >> 11:13:42.074742 IP (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto >> UDP (17), length 644) >> 179.252.225.2.5060 > 192.168.0.101.5070: SIP, length: 616 >> BYE sip:04833421234@200.193.70.69:5070 SIP/2.0 >> Via: SIP/2.0/UDP 179.252.225.2:5060 >> ;branch=z9hG4bK-d8754z-14cb719dd333c35c-1---d8754z- >> Max-Forwards: 70 >> Contact: <sip:9962@179.252.225.2:5060;transport=UDP> >> To: <sip:04833421234@200.193.70.69:5070>;transport=UDP >> From: <sip:9962@200.193.70.69:5070;transport=UDP>;tag=6f423601 >> Call-ID: ZTVhMDgwZTNjOTVhODk1ZjkwNGMzZTkyODgyZjk0N2E. >> CSeq: 3 BYE >> User-Agent: Zoiper r18976 >> Authorization: Digest >> username="9962",realm="asterisk",nonce="42d49556",uri=" >> sip:04833421234@200.193.70.69:5070 >> ",response="4911bfc1a62265954226f72e9b36d4b1",algorithm=MD5 >> Content-Length: 0 >> >> >> >> Em 13 de agosto de 2013 11:10, Jefferson B. Limeira < >> j...@internexxus.com.br> escreveu: >> >>> Firewall/linux ou baseado? >>> >>> Mostre o resultado de : >>> >>> # lsmod |grep sip >>> >>> Para debuggar tcpdump -i INTERFACE_LOCAL -s 0 -nn -v port 5060 >>> >>> Aqui minha martelada, aquela pode ser única e certeira ou não ajudar em >>> absolutamente nada... se fizer na interface interna e na externa, verá que >>> os pacotes são diferentes, teu firewall deve estar reescrevendo o pacote >>> SIP. Manda o resultado do lsmod e veja se tem os módulos de conntrack e nat >>> rodando... >>> >>> Em 2013-08-13 11:03, Fernando Trilha escreveu: >>> >>> Sim tenho um firewall no meio do caminho, mas liberei as portas pra >>> ele. >>> Como faço para debugar o sip? >>> -- >>> >>> -- >>> []'s Jefferson B. limeira...@internexxus.com.br(41) 9928-8628 >>> >>> >>> _______________________________________________ >>> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1; >>> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7; >>> Intercomunicadores para acesso remoto via rede IP. Conheça em >>> www.Khomp.com. >>> _______________________________________________ >>> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7. >>> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express. >>> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br. >>> _______________________________________________ >>> Para remover seu email desta lista, basta enviar um email em branco para >>> asteriskbrasil-unsubscr...@listas.asteriskbrasil.org >> >> >> >> >> -- >> Atte. >> Fernando Trilha >> Analista de Suporte >> 8414 - 6008 >> ftri...@gmail.com >> ::Soluções em informatica e redes corporativas:: >> >> _______________________________________________ >> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1; >> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7; >> Intercomunicadores para acesso remoto via rede IP. Conheça em www.Khomp.com. >> _______________________________________________ >> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7. >> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express. >> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br. >> _______________________________________________ >> Para remover seu email desta lista, basta enviar um email em branco para >> asteriskbrasil-unsubscr...@listas.asteriskbrasil.org >> >> >> >> -- >> []'s Jefferson B. limeira...@internexxus.com.br(41) 9928-8628 >> >> >> _______________________________________________ >> KHOMP: completa linha de placas externas FXO, FXS, GSM e E1; >> Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7; >> Intercomunicadores para acesso remoto via rede IP. Conheça em >> www.Khomp.com. >> _______________________________________________ >> ALIGERA – Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7. >> Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express. >> Channel Bank – Appliance Asterisk - Acesse www.aligera.com.br. >> _______________________________________________ >> Para remover seu email desta lista, basta enviar um email em branco para >> asteriskbrasil-unsubscr...@listas.asteriskbrasil.org >> > > > > -- > Atte. > Fernando Trilha > Analista de Suporte > 8414 - 6008 > ftri...@gmail.com > ::Soluções em informatica e redes corporativas:: > -- Atte. Fernando Trilha Analista de Suporte 8414 - 6008 ftri...@gmail.com ::Soluções em informatica e redes corporativas::
_______________________________________________ KHOMP: completa linha de placas externas FXO, FXS, GSM e E1; Media Gateways de 1 a 64 E1s para SIP com R2, ISDN e SS7; Intercomunicadores para acesso remoto via rede IP. Conheça em www.Khomp.com. _______________________________________________ ALIGERA Fabricante nacional de Gateways SIP-E1 para R2, ISDN e SS7. Placas de 1E1, 2E1, 4E1 e 8E1 para PCI ou PCI Express. Channel Bank Appliance Asterisk - Acesse www.aligera.com.br. _______________________________________________ Para remover seu email desta lista, basta enviar um email em branco para asteriskbrasil-unsubscr...@listas.asteriskbrasil.org