| [Internet] Asterisk fails to register with new SagemCom 2864 Hi
We had Bell Fibe installed this week-end.
Prior to this change, I had a working asterisk setup with a 2-Wire modem.
I replicated the port forward setup on SagemCom 2864, but asterisk fails to register on my VoiP provider.
I have forward port 5060 and 5062 to the asterisk computer, as well as 22 and 443.
Internet, ssh and https apache2 work fine.
I tried Zoiper and it failed to.
This is the output of asterisk:
Parsing '/etc/asterisk/cli.conf':
Found
*CLI> [Jan 28 17:00:19] NOTICE[4815]: chan_sip.c:13227 sip_reg_timeout: -- Registration for '8559421111@MyIvr?' timed out, trying again (Attempt #3)
[Jan 28 17:00:19] WARNING[4815]: chan_sip.c:3641 retrans_pkt: Retransmission timeout reached on transmission 0f0581ef07eca8b930de725679305ebd@technowait.com for seqno 102 (Critical Request) -- See »wiki.asterisk.org/wiki/display/ ... nsmissions Packet timed out after 60046ms with no response
[Jan 28 17:00:39] NOTICE[4815]: chan_sip.c:13227 sip_reg_timeout: -- Registration for '5144481111@MyIvr?2' timed out, trying again (Attempt #2)
What am I missing? |
|
zorxd
join:2010-02-05
Quebec, QC | Outbound SIP registration has nothing to do with port forwarding. So it should work without any special setting on the sagemcom.
Can you confirm internet is working on your asterisk box? (ping yourSIPprovider.com works) |
|
| ping to unlimitel.ca works 26.8ms average, but instead of showing a ping result every 2 seconds, it shows a result every 20 seconds.
ping to www.google.com shows results every 2 seconds, with 15.5ms average |
|
| reply to PierrotLafou
Hi,
Hi, I have the same proble in quebec city with bell fibe 50/50. I have asterisk & cloud/https servers who
-i can't acces to it from a local computer with the "dyndns" static
-i can't acces with the static lan ip
One of a bell tech i've seen on monday as said that i would call bell tech support(they really sucks) and then open a SECOND wan port on the sagecom modem, to seperate IPTV of my home lan.
I've call Bell and as usual, their customer service had said that it not support lan issue but F*** that, it's their firmware upgrade for IPTV at late november that makes the bug because that setup works between febuary to november
I had a ventrilo server to use push to talk in gaming...later than this firmware upgrade, i always use the "dyndns" static to connect to the server. By now, all the trafic landed to the hub (192.168.2.1) for me in my lan and my friends can still connect to the server! Note that i can't connect to the server thru the lan ip adresse since november and that make me very angry 
So, have you a solution? |
|
| said by Mguigui :Hi,
Hi, I have the same proble in quebec city with bell fibe 50/50. I have asterisk & cloud/https servers who
-i can't acces to it from a local computer with the "dyndns" static
-i can't acces with the static lan ip
One of a bell tech i've seen on monday as said that i would call bell tech support(they really sucks) and then open a SECOND wan port on the sagecom modem, to seperate IPTV of my home lan.
I've call Bell and as usual, their customer service had said that it not support lan issue but F*** that, it's their firmware upgrade for IPTV at late november that makes the bug because that setup works between febuary to november
I had a ventrilo server to use push to talk in gaming...later than this firmware upgrade, i always use the "dyndns" static to connect to the server. By now, all the trafic landed to the hub (192.168.2.1) for me in my lan and my friends can still connect to the server! Note that i can't connect to the server thru the lan ip adresse since november and that make me very angry
So, have you a solution?
did tech support enabled the second port as asked ? |
|
| Hello
Non ils n'ont rien régler et ils ne veillent pas le faire. Par contre, je crois ue je vais tout simplement les calisser dehors, méchante gang de noob et de débutant Bell |
|
|
|
1 edit | reply to PierrotLafou
It look like its a DNS problem.
It look to me there are 2 problems
1)
When I changed the DNS, in resolv.conf, from 192.168.2.1 to 8.8.8.8, asterisk works.
So the DNS programmed in the Sagemcom modem/router is not able to resolve the sip address.
2)
If I keep 192.168.2.1 in resolv.conf, but change the DNS in Sagemcom, from 207.164.234.129 to 8.8.8.8, this doesn't work. It look to me Sagemcom is not using it.
Any idea why new DNS from Bell doesn't work with SIP addresses ? |
|
