News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Outgoing calls with Zoiper (503 Service Unavailable / 603 media inactivity)

Started by Shanon, July 16, 2018, 03:51:43 PM

Previous topic - Next topic

Shanon

Hello,

I have Google Voice setup on SP1 on my OBi200.
SP2 is configured for use with Zoiper for calls via SP1. SP2 settings are similar to the ones in this post: Obi202/Zoiper for Android setup

When an outgoing call from Zoiper goes unanswered (after 20 s), the call ends abruptly with a "Service Unavailable" message. I am not able to make outgoing calls from Zoiper approximately for the next 5 minutes - calls end instantly with "Service Unavailable". Call history indicates "603 media inactivity".
This does not happen if I end the call before the ~20s limit.

The setup was working fine till firmware 5757. I have this problem since the new firmwares (5859+) got installed. The device is currently on 5898.

Screenshots: https://imgur.com/a/9wxDRQc

Syslog snippet from when the call fails:


02:40:33 192.168.1.14  RxFrom:c0a8999d:5060
02:40:33 192.168.1.14  INVITE sip:+18045551234@192.168.1.14:5061;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---bcca30b66ec232d3;rport#015#012Max-Forwards: 70#015#012Contact: <sip:200000@192.168.1.12:5060;transport=UDP>#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 1 INVITE#015#012Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE#015#012Content-Type: application/sdp#015#012User-Agent: Zoiper rv2.8.87-mod#015#012Allow-Events: presence, kpml, talk#015#012Content-Length: 247#015#012#015#012v=0#015#012o=Zoiper 0 0    IP4 192.168.1.12#015#012s=Zoiper#015#012c=   IP4 192.168.1.12#015#012t=0 0#015#012m=audio 37836 RTP/AVP 0 101 8 3#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:3 GSM/8000#015#012a=sendrecv#015
02:40:33 192.168.1.14  sendto c0a8999d:5060(521)
02:40:33 192.168.1.14  SIP/2.0 401 Unauthorized#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 1 INVITE#015#012Content-Length: 0#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---bcca30b66ec232d3;received=192.168.1.12;rport=5060#015#012WWW-Authenticate: Digest algorithm=MD5,nonce="dfdf998e8F5A56D0",opaque="effe301cbdfffff9",realm="pnn.obihai.com",nonce="E69E2EC0",response="E69E2EC0E69EEEC0EEEE2EC0E69E2EC0"#015#012#015
02:40:33 192.168.1.14  RxFrom:c0a8999d:5060
02:40:33 192.168.1.14  ACK sip:+18045551234@192.168.1.14:5061;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---bcca30b66ec232d3;rport#015#012Max-Forwards: 70#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 1 ACK#015#012Content-Length: 0#015#012#015
02:40:33 192.168.1.14  RxFrom:c0a8999d:5060
02:40:33 192.168.1.14  INVITE sip:+18045551234@192.168.1.14:5061;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---141eb093cbb26dc6;rport#015#012Max-Forwards: 70#015#012Contact: <sip:200000@192.168.1.12:5060;transport=UDP>#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 2 INVITE#015#012Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE#015#012Content-Type: application/sdp#015#012User-Agent: Zoiper rv2.8.87-mod#015#012Authorization: Digest username="200000",realm="pnn.obihai.com",nonce="dfdf998e8F5A56D0",uri="sip:+18045551234@192.168.1.14:5061;transport=UDP",response="337a3fb8e5775666d5b4619aed38d39d",algorithm=MD5,opaque="effe301cbdfffff9"#015#012Allow-Events: presence, kpml, talk#015#012Content-Length: 247#015#012#015#012v=0#015#012o=Zoiper 0 0    IP4 192.168.1.12#015#012s=Zoiper#015#012c=   IP4 192.168.1.12#015#012t=0 0#015#012m=audio 37836 RTP/AVP 0 101 8 3#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:3 GSM/8000#015#012a=sendrecv#015
02:40:33 192.168.1.14  sendto c0a8999d:5060(398)
02:40:33 192.168.1.14  SIP/2.0 100 Trying#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 2 INVITE#015#012Content-Length: 0#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>;tag=SP2dffaf3ebdefe0b72#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---141eb093cbb26dc6;received=192.168.1.12;rport=5060#015#012Server: OBIHAI/OBi200-3.2.2.5898#015#012#015
02:40:33 192.168.1.14  CCTL:NewCallOn Term 10[0] 200000->,+18045551234
02:40:36 192.168.1.14  RTP:DtmfTxMtd:1(1),0
02:40:36 192.168.1.14  SIP/DLG:Start Early ICE on 18x
02:40:36 192.168.1.14  sendto c0a8999d:5060(527)
02:40:36 192.168.1.14  SIP/2.0 180 Ringing#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 2 INVITE#015#012Content-Length: 0#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>;tag=SP2dffaf3ebdefe0b72#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---141eb093cbb26dc6;received=192.168.1.12;rport=5060#015#012Server: OBIHAI/OBi200-3.2.2.5898#015#012Contact: <sip:200000@192.168.1.14:5061>#015#012Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE#015#012#015
02:40:36 192.168.1.14  RTP:Start->4a7d2716:19305(80 0);0;0;0:0:0;0(46)
02:40:36 192.168.1.14  RTP:Set actpass 2
02:40:36 192.168.1.14  DTLS:Setup active
02:40:36 192.168.1.14  DTLS:Handshake Success
02:40:37 192.168.1.14  RTP:PeerRflxAddr=4a7d2716:19305
02:40:40 192.168.1.14  SRTCP:index=80000001
02:40:40 192.168.1.14  RTCP:RxMuxPkt[60]=200<--4a7d2716:19305
02:40:45 192.168.1.14  SRTCP:index=80000002
02:40:45 192.168.1.14  RTCP:RxMuxPkt[60]=200<--4a7d2716:19305
02:40:50 192.168.1.14  SRTCP:index=80000003
02:40:50 192.168.1.14  RTCP:RxMuxPkt[60]=200<--4a7d2716:19305
02:40:55 192.168.1.14  SRTCP:index=80000004
02:40:55 192.168.1.14  RTCP:RxMuxPkt[60]=200<--4a7d2716:19305
02:40:57 192.168.1.14  PRD:1st down
02:40:57 192.168.1.14  sendto c0a8999d:5060(411)
02:40:57 192.168.1.14  SIP/2.0 503 Service Unavailable#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 2 INVITE#015#012Content-Length: 0#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>;tag=SP2dffaf3ebdefe0b72#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---141eb093cbb26dc6;received=192.168.1.12;rport=5060#015#012Server: OBIHAI/OBi200-3.2.2.5898#015#012#015
02:40:57 192.168.1.14  RTP:Del Channel
02:40:57 192.168.1.14  RTP:Del Channel
02:40:57 192.168.1.14  RxFrom:c0a8999d:5060
02:40:57 192.168.1.14  ACK sip:+18045551234@192.168.1.14:5061;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG5bK-524387-1---141eb093cbb26dc6;rport#015#012Max-Forwards: 70#015#012To: <sip:+18045551234@192.168.1.14:5061;transport=UDP>;tag=SP2dffaf3ebdefe0b72#015#012From: <sip:200000@192.168.1.14:5061;transport=UDP>;tag=3551f64c#015#012Call-ID: AUDPX5HHvWARiqXVFuHjeQ..#015#012CSeq: 2 ACK#015#012Content-Length: 0#015#012#015
02:40:58 192.168.1.14  TCP:Broken Connection(spreg) 35 -1
02:40:58 192.168.1.14  REG:HandleTcpEvent 3;wc=0




SP1 "restarts" after a few minutes & everything starts working again:



02:44:00 192.168.1.14  SP1:Restart TCP Connect:c0a8999c:4116->4009f36c:5061
02:44:00 192.168.1.14  TLS-EXT Hostname:obihai.telephony.goog
02:44:00 192.168.1.14  TCP:Connect OK(spreg)35
02:44:00 192.168.1.14  Trying to connect ssl
02:44:01 192.168.1.14  TC:ssl connected
02:44:01 192.168.1.14  REG:HandleTcpEvent 2;wc=1
02:44:02 192.168.1.14  PRD:1st success
02:44:02 192.168.1.14  PRD:NOPriFbToTry
02:47:09 192.168.1.14  RxFrom:c0a8999d:5060



Any help is appreciated.


Edit:
1. Added syslog for the bit where SP1 "restarts"
2. Updated topic subject
3. Screenshot link from a later post (attachments are still failing for some reason)

drgeoff

Recent OBi20x firmwares appear to have a bug which prevents some IP phones (hard or soft) from registering to them.  If Zoiper can be set to call without registration, try that.

azrobert

#2
After 5757 the OBi200 stopped working as a proxy server for some devices and won't accept registration. The 401 Unauthorized in the syslog indicates that is what's happening to you. You can verify this by looking at the OBi200 system status. SP2 should show Local_Client followed by the IP address of the device running Zoiper. If you don't see the IP address, Zoiper isn't registered.

Try this:
Service Providers -> ITSP Profile B SIP -> X_Proxy: unchecked

Zoiper can still call when unregistered. You can also tap "Unregister" in Zoiper.

Edit:
I already wrote the above when I saw drgeoff already told you about the bug and didn't feel like changing my post. You still need to uncheck X_Proxy. You will get the unauthorized if you don't.

Shanon

Thanks for the quick replies!

I tried with Zoiper unregistered. No luck.

I will try with X_Proxy unchecked & post an update.


Shanon

I could not find X_Proxy under ITSP Profile B SIP.
I unchecked Voice Services ->  SP2 Service -> X_Proxy.
No change. I got the same error message.
I also tried after clearing Outbound Proxy in Zoiper. Same error.

The call history indicates (603 media inactivity) as the reason with or without registering/X_Proxy changes.

I am not able to attach files to the post. Here are some screenshots: https://imgur.com/a/9wxDRQc

azrobert

There are a few posts reporting a 603 error. I don't see a resolution. Here is one:
http://www.obitalk.com/forum/index.php?topic=14270.0

Are you running the current firmware? I'm running 5859 and Zoiper on an Android works for me with X_Proxy disabled. 5897 introduced several bugs.  5898 fixed the bugs and is the current version.

A_Friend

I'm intrigued.  I didn't know you could register zoiper as SP2, etc.  Can someone explain, in macro terms, how this is set up?

I currently use zoiper on a smartphone, remotely, as a local extension (subaccount) via voip.ms, to call another subaccount which resides on an Obi202, from which I use AutoAttendant in conjunction with my speed dials.  It works well and it's not particularly cumbersome, but it seems like I've got unnecessary layers compared to what you're doing.

Shanon

Quote from: azrobert on July 17, 2018, 12:14:05 PM
There are a few posts reporting a 603 error. I don't see a resolution. Here is one:
http://www.obitalk.com/forum/index.php?topic=14270.0

Are you running the current firmware? I'm running 5859 and Zoiper on an Android works for me with X_Proxy disabled. 5897 introduced several bugs.  5898 fixed the bugs and is the current version.


I am running the latest 5898. Zoiper is on Android and works fine (incoming/outgoing) but for the unanswered call scenario.
Zoiper <-> OBi stops working for about 5 minutes once it goes into the "Service Unavailable" state.

Are your OBi & Zoiper settings similar to the ones in the post I mentioned earlier?


azrobert

Quote from: Shanon on July 17, 2018, 01:37:33 PM
Are your OBi & Zoiper settings similar to the ones in the post I mentioned earlier?

Yes, the part that counts is the same. I just tried calling another GV number. I let it ring until GV voicemail picked up. No 603 error.

azrobert

#9
Quote from: A_Friend on July 17, 2018, 12:53:59 PM
I'm intrigued.  I didn't know you could register zoiper as SP2, etc.  Can someone explain, in macro terms, how this is set up?

This setup is basically for WiFi on your local network. Some people have had some success outside their local network with some OBi setting changes. I never got it to work reliably.  See 2nd option here:

http://www.obitalk.com/forum/index.php?action=dlattach;topic=12895.0;attach=2230

There is a reliable method for remote access. It uses the Android softphone CSipSimple and requires the free Sip2Sip service. This method doesn't use the Auto Attendant. If you're interested, please open a new topic and I'll show you the setup. I haven't used this in years and hope nothing has changed.

Edit:
I just tried the Sip2Sip method and it still works.
CSipSimple can pass the outbound number plus your public IP address to sip2sip.
sip2sip forwards the call to your public IP.
Your router port forwards the call to your OBi.
Forwarding the call thru sip2sip eliminates the audio problems other methods have.

Shanon

Quote from: azrobert on July 17, 2018, 02:09:50 PM
Yes, the part that counts is the same. I just tried calling another GV number. I let it ring until GV voicemail picked up. No 603 error.

Thank you!

I hope the next version of the firmware has a fix for this bug.


Shanon

Quote from: azrobert on July 17, 2018, 12:14:05 PM
I'm running 5859 and Zoiper on an Android works for me with X_Proxy disabled.

I got hold of an OBi200 still on 5859 & tried the same setup. No luck  :(