Echo test does not answer

theMightyMacBoy

Silver Partner
Advanced Certified
Joined
Mar 21, 2017
Messages
48
Reaction score
5
I have a client who I am working with who is having issues with the Echo Test not answering from any phone. When Echo Test is called you get this message: "Calls number does not exist"

When looking at the logs I see this.

10/15/2024 11:46:15 AM - [CM503014]: Call(C:96610): No known route from Extn:475 to target: <sip:*[email protected]:5060/UDP>
10/15/2024 11:46:15 AM - Call(C:96610): from Extn:475 to *777 doesn't match any outbound rule. No outbound rule could be selected.
10/15/2024 11:46:15 AM - [Flow] Target endpoint for *777 can not be built!
10/15/2024 11:46:15 AM - [CM503010]: Call(C:96610): Making route(s) from Extn:475 to <sip:*[email protected]:5060/UDP>

I have gone into System Parameters and verified that *777 is the correct dial code for Echo Test. When updating this parameter, I see this in the logs.

10/15/2024 11:45:19 AM - [CM504001]: Endpoint ParkOrb:*777: new contact is registered. Contact(s): [sip:*[email protected]:5483 / *777]
10/15/2024 11:45:04 AM - [CM504002]: Endpoint ParkOrb:*777: a contact is unregistered. Contact(s): []

Has anyone seen this? v18 U9 on Debian. (This client is scheduled for upgrade before end of year. They are hard to schedule anything with!)
 
Try without the"*"
 
In your System Extensions page, do you see the system extension as registered?

1729070713454.png

1729070727782.png

Then go to your dial codes, and see if you have a conflicting dial code.

1729070779059.png

Those shown are the default dial codes which should not conflict with anything else on the system.
 
  • Like
Reactions: theMightyMacBoy

Members Online Now

Forum statistics

Threads
111,860
Messages
589,437
Members
164,700
Latest member
Apollo Cloud