SIP phones no longer connected after 3.2.1 (Build: 5794EX) Saturday 1/21/18

<< < (11/13) > >>

SteveInWA:
Quote from: lottamoxie on May 11, 2018, 05:33:15 pm

Obi 200 here.  Was converted to new firmware several days ago.

My problem is this:

Inbound calls, my cordless phone rings once and then stops.  The caller on their end is hearing a type of "number not in service" message.

I have no problem making outbound calls, I get a dialtone and everything works normally.

My GV status shows as connected on the Obitalk dashboard.

Any ideas?



Hi there:

The "...not in service..." message takes a bit of problem isolation to determine what's wrong.

Using a desktop/laptop computer's web browser, sign into your Google / Gmail account and then go here:

https://voice.google.com/settings

Delete all the linked telephone numbers off of the list.  Turn on "do not disturb" mode.  Call your inbound Google Voice phone number from some other phone number.  What happens, exactly?  The expected behavior is that the caller will be immediately sent to your Google Voice voicemail greeting.

BlakeN:
Quote from: azrobert on May 11, 2018, 08:58:27 am

Try this:
SP4 X_InboundCallRoute: ph

When you make a call, does the OBi200 phone port ring?
If the phone doesn't ring, the call isn't getting to the OBi200 and I don't know why.
Do not do the following steps,

If the phone rings, do the following:
SP4 X_InboundCallRoute: sp4($1@192.168.1.99)

Dial a number on the IP phone, wait a few seconds and hang up.
You will not hear anything after dialing the number.

Now do this:
SP4 X_InboundCallRoute: sp4($2@192.168.1.99)

Make another call for a few seconds.

$1 contains the IP phone's userid and $2 the outbound number.
You should be able to see these in the OBi200 call history.

To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser and hit Enter
The UserID and default Password are both "admin".
Click Status on the left column then click Call History.

What does the call history show for those calls?



With forcing user ID unchecked call does get to OBI.  I get the following in the call log.  I have not had any time to further debug.  I will try your suggestion above when I have time (It has been a busy weekend).
 
Call 1   05/11/2018    11:06:16   
11:06:16   From SP4(1002)   To SP1(1234567890)
11:06:18      Call Ended (488 Not Acceptable Here)

BTW - I put a ticket in on the 1062 - no upgrade of code and no GV.  They upgraded code and now both GV on 1062 seems to work.  They said to delete and add the GV one on the 200 that would not connect.  It still does not work - same connecting to 63.9.242.172.

Thanks again for the help

azrobert:
Quote from: BlakeN on May 12, 2018, 01:36:07 pm

I will try your suggestion above when I have time (It has been a busy weekend).


Don't bother doing those tests. Your call history shows everything is being routed correctly. I don't know why you're getting the 488 error. Can you make a call from the phone port?

Blake4913:
Quote from: azrobert on May 12, 2018, 01:53:55 pm

Quote from: BlakeN on May 12, 2018, 01:36:07 pm

I will try your suggestion above when I have time (It has been a busy weekend).


Don't bother doing those tests. Your call history shows everything is being routed correctly. I don't know why you're getting the 488 error. Can you make a call from the phone port?

yes, the phone port works great in both directions.  Probably would be hard to sell devices if it did not.  There is likely no incentive for Polycom to allow a Cisco phone to work or any SIP phone for that matter.  I submitted a ticket and included all three of my issues.  They jumped right on the 1062 issue (its fixed), tried to give some advice on the one 200 that won't connect to GV (no luck to fix) and ignored the SIP phone issue.  Even gave the issue that one of the others in this chain figured out by sniffing the packets.   

azrobert:
It seems the 488 error is a codec problem.
See:
https://supportforums.cisco.com/t5/ip-telephony/message-sip-with-488-not-acceptable-here/td-p/2077189

The link suggests forcing G711a, but I know GV works with G711u. I checked my OBi200's codec profile and the G711a codec is disabled. I don't remember if I disabled it. Check which codec profile your GV is using then see whether any codecs in that profile are disabled. See if you can force G711u in your Cisco phone.

Navigation

[0] Message Index

[#] Next page

[*] Previous page