 Thread: RE: SIP response 482 "Loop Detected" |
|
|
Before opening this thread I have made a few tests, including different stun servers and placing the phone at the DMZ.
Since the last post, the service has become more stable - what made troubleshooting even worse. It used to go down every day around a certain time and go up precisely 02:00am. Since May 6th, I have noticed only these flaws:
May 7 17:59:14 (last registration of the day)
May 8 02:01:46 (first registration of the day)
May 11 02:05:13 (this was a completely atypical day)
May 11 07:46:41
May 11 18:57:03
May 12 02:02:43
May 13 19:20:15
May 14 02:01:07
These were the only interruptions from May 6 to May 15. As they appear in random days, I couldn't isolate a root cause - be it the IP cameras, the desktop monitoring application or the ISP. Taking a shot at the SIP now, waiting for them to reply my trouble ticket.
Any updates will be shared with you.
Regards
|
|
| Thread: RE: SIP response 482 "Loop Detected" |
|
|
The current topology is:
Internet
ISP Firewall/NAT
our Internet link
Linksys 524 wifi router
computer 1|| computer 2 || IP cameras || IP Phone
All devices are wired to the router. IP cameras connect to the computer 2, which also has an always-active LogMeIn account (for remote control).
Computer 1 is only used for registering sales.
The IP Phone (Intelbras TIP 100) is connected to the router.
There are no ATAs or softphones in this network.
We are behind 2 NAT, the ISP's and ours. However, STUN is dealing fine with them.
We'll shut them all down during the weekend to test.
Thank you again.
|
|
| Thread: RE: SIP response 482 "Loop Detected" |
|
|
Hello Diafora,
as I wrote on the update, the Loop Detected happens in 3 extensions, each of them in a separate location. They have, though, the same ISP, what may be causing the message. However, I realized it is not affecting my service.
The real problem, as I later verified, is that one extension (ext. 102) stops registering during the day and becomes unavailable for all calls, inbound, outbound or internal.
At 2 am (everyday) it starts registering again. Magically. Or else, if the phone is cold booted (pull the power plug) it also goes back to work.
The ISP committed to make some investigation, but I have no idea where the real problem is. I'll try to change the IP phone as well, to be sure it is not some device bug.
Thanks for your help!
|
|
| Thread: RE: SIP response 482 "Loop Detected" |
|
|
UPDATE
Checking on system log on a daily basis, I could realize one of my extensions stops registering every day (usually circa 18:00h) and starts registering again in the following day at 02:00 am (all times considering America/Sao Paulo timezone, on www4).
Is there any server or configuration reset taking place at this time?
Any help is appreciated.
===========================================
Hello,
I am having some issues with one of my extensions. Sometimes, in the middle of the day, it refuses to re-register. It is apparently working, but calls cannot be completed - inbound or outbound.
Checking on the system log, I found the following message:
VERBOSE[115047] logger.c: -- Got SIP response 482 "Loop Detected"
I don't know what could have caused it. All of my extensions are in separate offices (one per office), all of them are working fine - except for this one.
Any ideas?
Thanks
Update: the Loop Detected message is not actually affecting any functionality, as far as I know. Despite this message, calls are completed normally.
|
|
| Thread: RE: www2 backup not the same as www4 |
|
|
My account is not working either.
Phones don't register, DID's don't forward calls.
I manually moved my account to www2 server, and some extensions started working again. Some.
|
|
| Thread: RE: Account blocked |
|
|
Hello,
this morning my PBXes account was blocked, stating I had used more minutes than my quota allows. According to the Usage screen, I used 5855 minutes in December. I won't question that, this was a really busy month.
However, in December I bought a second Premium subscription for this account, what should grant me 10,000 minutes per month. Isn't this correct?
I had to buy another Premium subscription today to have my extensions back, but I am certainly not happy to have a third subscription without the need of it.
Please advise.
|
|
| Thread: RE: DID mismatch in PBXes |
|
|
Again today.
Just for the record, these transient errors come and go for no apparent reason.
I have mapped my DID to a Voxalot account and it worked. Mapping it to PBXes returns the "No Answer" message.
Considering the history, this will be solved by the morning, but it is so uncomfortable to trust on luck...
EDIT
I tried to change the www server to see where the problem was. All servers tested, none worked.
Looking at the Call Monitor, all inbound calls are shown as Destination "s"; Context "aa_1"; App "Hangup"; Duration around 10 sec.
This means that, from PBXes side, the call was answered, directed to the Auto Attendant for 10 sec and then hung up.
From the dialers' perspective, however, 10 seconds of silence were heard before the "no answer" or busy tone signal was received.
Solution: The DID provider I use has 3 servers. This problem is happening only with USA server; moved the DID to the UK server and it started working again.
EDIT 2
Again today, Jan. 14th 2011.
DID from DIDWW.com was not working this morning with PBXes, but it worked normally after I configured it to Betamax clones, Voxalot and others.
Does PBXes provide us any list of suggested, reliable and/or supported DID providers?
|
|
| Thread: Your call cannot be completed as dialed |
|
|
Hi all,
when making outbound calls, I hear the following message:
Your call cannot be completed as dialed. Please try again later.
I have tried to change the server (www2, www3, www4), changed the trunks, re-configured the passwords, Submit&Start... and nothing.
Seems like a revival of post http://www1.pbxes.com/forum/thread.php?t...1283187314&sid=
System Log shows:
Nov 8 20:35:22 VERBOSE[99081] logger.c: -- SIP/TroncoSIP-2b84 is circuit-busy
Nov 8 20:35:22 VERBOSE[99081] chan_sip.c: Hangup call SIP/TroncoSIP-2b84
Nov 8 20:35:22 VERBOSE[99081] logger.c: == Everyone is busy/congested at this time (1:0/1/0)
Nov 8 20:35:22 VERBOSE[99081] logger.c: -- Playing 'cannot-complete-as-dialed' (language 'en')
Nov 8 20:35:25 VERBOSE[99081] logger.c: -- Playing 'pls-try-call-later' (language 'en')
Nov 8 20:35:27 VERBOSE[99081] chan_sip.c: Hangup call SIP/cacaushow-102-1259, SIP callid e90bc11b6872c44e@TkJfTUNOT0dVRUlSQS5pdGF1dGVjLmludHJhbmV0
|
|
| Thread: RE: Trunk Dial Rules |
|
|
telagente00,
thank you for the anwer. Could you please elaborate on it?
My system log shows numbers I can't recognize, such as
14492bec61310bdc2fd3b7531e55dc0c@[SIP Trunk IP address]
How can I know which digits were actually dialed?
Thank you
|
|
| Thread: RE: Trunk Dial Rules |
|
|
Hello,
simple question:
I want to add 021 to the local numbers I dial in Trunk 1, so I added this line in Dial Rule (in Trunk 1 menu)
021+NXXXXXXX (all local numbers are 8-digit long)
But the Call Monitor shows all calls sent exactly as dialed (no conversion).
Any idea?
|
|
| Thread: RE: Mini Page |
|
|
This worked for me:
1- Go to the mini page
2- LOG OUT (simply closing the browser isn't enough)
3 - close the browser
4 - delete cookies/history/offline content
5- go to www.pbxes.com
6- log in
Let me know if that works for you as well.
Regards
|
|
| Thread: RE: DID mismatch in PBXes |
|
|
This morning my DID stopped working.
I opened a ticket with my DID provider and, after some tests, we came to the conclusion the problem is with my account only.
Could you moderators please take a look?
When connecting via the DID we hear a busy tone. When connecting directly from another SIP device (a softphone calling cacaushow@pbxes, for instance) call is completed normally.
Call monitor shows the incoming calls as destination S and context macro-hangupcall.
|
|
| Thread: RE: Network Outage Update issue |
|
|
skyslabo,
I had the same problem this morning. Looks like PBXes didn't fully recover from the outage yesterday.
Log in to your account, select Personal Data and then click Submit & Start. I did it and my extensions were automatically restored.
Good luck!
|
|
|
