Jump to content

Problem with configuration


Wolverinext2

Recommended Posts

hello, i need help me. i have problems whit the configuration of express talk and axon.

 

14:59:01 Running SIP Network Tool

14:59:03 Server 192.168.1.80 did not respond to register (user 101)

14:59:03 Check server details for that line

14:59:03 Register attempt for proxy 192.168.1.80 failed

14:59:03 501 Not Implemented

14:59:11 Restarting the SIP Engine so settings take effect.

14:59:13 SIP Private IP is: 192.168.1.80:5060

14:59:13 SIP Public IP is: 192.168.1.80:5060

14:59:13 SIP Number: 101@192.168.1.80:5060

14:59:13 Register attempt for proxy 192.168.1.80 failed

14:59:13 501 Not Implemented

14:59:14 Initiated sip call to: 102

14:59:14 Error returned: Request Pending

14:59:14 Call has disconnected

14:59:24 Register attempt for proxy 192.168.1.80 failed

14:59:24 501 Not Implemented

14:59:35 Register attempt for proxy 192.168.1.80 failed

14:59:35 501 Not Implemented

14:59:45 Register attempt for proxy 192.168.1.80 failed

14:59:45 501 Not Implemented

14:59:55 Server 192.168.1.80 did not respond to register (user 101)

14:59:55 Check server details for that line

14:59:55 Register attempt for proxy 192.168.1.80 failed

14:59:55 501 Not Implemented

 

 

Plis help me

Link to comment
Share on other sites

  • 3 months later...
  • 3 years later...

Hi all,

Looking at the issue it appears that you may need to contact support but please realize the following...

 

It appears that the log in question is from Express Talk. Whatever you are trying to register with is returning “501 Not Implemented” in response to the REGISTER. Some things that may be happening:

 

- You are using Express Talk on port 5060 and are pointing it to register on the same box with the default port. This would mean ET gets the register and returns a glaring NO as expected.

- Whatever you are running that intercepts the message (i.e. not Axon) doesn’t support REGISTER (or at least not with the provided credentials)

- There may be some other unique configuration issue that causes this that I couldn’t tell you without a SIP log from ET and Axon (to start) so you would need to contact support.

 

In any case this looks like it is a user-related issue and most likely not a bug with the software. Hopefully this points you all in the right direction. Again, if you need more assistance this would be best taken up with NCH support.

cheers

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...