I was setting up a SIP station using a Grandstream GXP-2000 and ran into a problem where the phone could call out, but if another phone tried to call it they would receive a busy signal. I tried a Polycom phone in its place and ran into the same thing. What made it start working was rebooting the IP Office.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP Office SIP Endpoint can make calls but not recieve them
- Thread starter thosfiore
- Start date
- Status
amriddle01
Programmer
A good old reboot is almost as good as a hammer when it comes to making things work 
RodneyMcSnow
Technical User
Sometimes a reboot is needed.jm
RodneyMcSnow
Technical User
Upon a reboot of the ipoffice this forces sip endpoints to re register and download any needed files via tftp.
What options are enabled on the ipoffice? Are you using lan1 or lan2 for sip registration?
Static or dhcp?
What version ip office?
What options are enabled on the ipoffice? Are you using lan1 or lan2 for sip registration?
Static or dhcp?
What version ip office?
- Thread starter
- #5
The phones weren't downloading any software from the IP Office or any TFTP server. I would think that rebooting and powering each of them down several times would have re-registered them.
LAN1, which is setup with a static IP address is the LAN used for the SIP phones. The phones themselves are using DHCP.
I'm not sure what you mean by options that are enabled. I basically followed the documentation for setting up third party SIP phones.
The IP Office version is 6.1.22.
This may have just been a quirk of how I setup the phones, but I did see a different thread from last year where someone had the same issue and the tread just trailed out without a resolution listed.
As far as a good old reboot, it may be what is needed, but it isn't the easiest thing in the world to arrange on a system of any size.
Thanks for all of your comments.
LAN1, which is setup with a static IP address is the LAN used for the SIP phones. The phones themselves are using DHCP.
I'm not sure what you mean by options that are enabled. I basically followed the documentation for setting up third party SIP phones.
The IP Office version is 6.1.22.
This may have just been a quirk of how I setup the phones, but I did see a different thread from last year where someone had the same issue and the tread just trailed out without a resolution listed.
As far as a good old reboot, it may be what is needed, but it isn't the easiest thing in the world to arrange on a system of any size.
Thanks for all of your comments.
montyzummer
IS-IT--Management
you can reboot single sip phones through the monitor application , but i would run some traces check you are getting correct messaging with only the sip filters ticked , call between sip device and sip device and then back again and see the real time log the monitor trace to file .
then google sip messages and by getting a sip message / response list and comparing it with your monitor trace (not under the status tab that will give you a real view time view and hopefully clue and will let you reboot the phone individually)look at what the sip trace log says it looks complicated at first but TX at the start of say a 100 messsage is what the phone is sending and then RX is what it is getting back from your far end.
you usually get x2 bad responses first then from there follow the trace it does become easier it will probably be authentication , if you struggle post and hopefully , I can give you some debugging clues. And between us solve the proble , plus post youre config
APSS (SME)
ACSS (SME)
then google sip messages and by getting a sip message / response list and comparing it with your monitor trace (not under the status tab that will give you a real view time view and hopefully clue and will let you reboot the phone individually)look at what the sip trace log says it looks complicated at first but TX at the start of say a 100 messsage is what the phone is sending and then RX is what it is getting back from your far end.
you usually get x2 bad responses first then from there follow the trace it does become easier it will probably be authentication , if you struggle post and hopefully , I can give you some debugging clues. And between us solve the proble , plus post youre config
APSS (SME)
ACSS (SME)
- Status
Similar threads
