After V20 Upgrade / Error 30051

[AndyThe327st]

Hi!

I just upgraded our PBX over the weekend to v20. After the upgrade I made a backup and then a fresh install + restore because I had to switch to GEN2 in Hyper-V for performance and security reasons (secure boot).

When trying to make an outbound call from a telephone I am now getting an error 30051 (123456789 is the number being called, I replaced our domain name) and the call is not being placed:

Unidentified Incoming Call. Review INVITE and adjust source identification: INVITE sip:[email protected]:5160;transport=UDP;tag3cx=rn5jduxr SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjyYtKWREVSuy2mBu.bTRhJfUJN8jV3di0;rport=5080 Via: SIP/2.0/UDP 37.135.57.4:50214;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-d2q9a2ag9v07hebz9cjt1ys.4e.0j.3o_9718316 Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPjyYtKWREVSuy2mBu.bTRhJfUJN8jV3di0;alias Max-Forwards: 69 Record-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.0-d2q9a2ag9v07hebz9cjt1ys.4e.0j.3o_9718316> Contact: "Doe, John"<sip:[email protected]:5060;rinstance=0-d2q9a2ag9v07hebz9cjt1ys.4e.0j.3o> To: <sip:[email protected]:5160;tag3cx=rn5jduxr> From: "Doe, John" <sip:[email protected]:5160>;tag=x-p9Io1Y3ek5WHDwkS80hs1BwiJo8bvf Call-ID: KuXdrROwy.ioGGZ28ei3tbE.Q1wCsgi3 CSeq: 26836 INVITE Session-Expires: 1800 Min-SE: 90 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Content-Type: application/sdp Supported: replaces, 100rel, timer, norefersub User-Agent: 3CXPhone for iOS 20.0.1.25 Content-Length: 441 v=0 o=- 3919154632 3919154632 IN IP4 192.168.2.44 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 10002 RTP/AVP 9 8 0 18 125 101 c=IN IP4 192.168.2.44 b=TIAS:96000 b=AS:117 a=rtcp:10003 a=sendrecv a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:125 opus/48000/2 a=fmtp:125 useinbandfec=1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 0 RTP/AVP 31 c=IN IP4 127.0.0.1

Is this correct: <sip:[email protected]:5160> or should it be like <sip:[email protected]:5160>

Am wondering where I can adjust the source identification?

Anyone got any idea?

Best regards,
Andy

 

[AndyThe327st]

It seems to affect only one phone. Tried with another device and it can place calls. Maybe I need to reprovision it. It's not a support device.

 

[Alphabetic]

You should compare a capture from the working call and non working and see what the differences are.

 

[AndyThe327st]

Hm, is that already helpful.

I have the following setup:
An Android phone (extension 101) which can place calls.
An Iphone phone (extension 100) which cannot place calls.
The 3CX Desktop App (extension 100) which can place calls.
A Gigaset Go Box (unsupported) (with extension 100/101) which cannot place but receive calls.

I tried to make a trace of a call from the Gigaset Go Box, but did not find any SIP traffic in the trace.

Therefore I trace the Android phone calling from 101 to 100, which works and looks like this (i hung up therefore cancelled):
View attachment 40230

I tried the same with the iPhone in the other direction (100 to 101) which looks like this:
View attachment 40232

A big difference is that the working one has COMPANY.ELASTIX.COM in the From column. The non-working one has COMPANY.COM.

Inside of the Android and iPhone app when looking at accounts, both show PBX Local as Company.Com and PBX External as Company.Elastix.Com, just like we had it running before.

And thoughts?

EDIT: Sorry killed the attachment. Will upload them soon again.

Andy

 

[Alphabetic]

Where are you seeing the local PBX settings? v20 uses just one FQDN with split DNS if needed.

I've got a v20 on my mobile app and cant see these - are you running latest app on the iphone? Try reprovisioning.

 

[AndyThe327st]

On Androind under Settings -> Accounts -> Administer account.

On iphone under Menu -> Accounts -> Details.

Both show different DNS names for local and external.

I tried to reprovision the iphone but it does not show up under Phones in the Admin interface. Is that normal? The Android shows up.

 

[Alphabetic]

on the phone are you using v20.0.1.25?

 

[AndyThe327st]

It shows 20.0.0.1620

EDIT: Sorry, that's the server. It is 20.0.1.25 under About.

 

[Alphabetic]

im on iphone, i dont have a details under accounts only a ">" which gives me name, ext and server and i've only got the one.

 

[AndyThe327st]

im on iphone, i dont have a details under accounts only a ">" which gives me name, ext and server and i've only got the one.

Yes, didn't like the ">" so I called it Details. I got two there. Can this be changed or does it mean reinstall / restore?

 

[Alphabetic]

Ok, i just tested on a customer who is on prem and i can see that internal PBX too. Local PBX shows the IP.

So, is your local PBX resolvable on the network then? if not, it would fail to the external PBX.

what happens if you call *777 from the iphone? Is the iphone on the wifi the PBX is on? What happens if you try off the wifi?

 

[AndyThe327st]

No, that name is our domain's root name COMPANY.COM. That won't resolve to a PBX anywhere. It resolves to our WWW server instead.The external one COMPANY.ELASTIX.COM works though from everywhere.

Tried to call *777 and it works only from the Android. When calling it from the iPhone it is as if I called an external number and I get the same logging:
Unidentified Incoming Call. Review INVITE and adjust source identification: INVITE sip:*[email protected]:5160;transport=UDP;tag3cx=ayaebiuy SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---PjiPtcUzpq5c8LFYyDQeB3eYs9fKDvL8RQ;rport=5080 Via: SIP/2.0/UDP 90.167.50.11:22673;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-mnn.xzpu0c3hesb4ng5ywf4p-hoi.0kj_15830620 Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPjiPtcUzpq5c8LFYyDQeB3eYs9fKDvL8RQ;alias Max-Forwards: 69 Record-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.0-mnn.xzpu0c3hesb4ng5ywf4p-hoi.0kj_15830620> Contact: "Doe, John"<sip:[email protected]:5060;rinstance=0-mnn.xzpu0c3hesb4ng5ywf4p-hoi.0kj> To: <sip:*[email protected]:5160;tag3cx=ayaebiuy> From: "Doe, John" <sip:[email protected]:5160>;tag=.lU-0D4KpnEfXPq8KA6XHZ4NBIpbHX7i Call-ID: E3WmfXVGfHDL3Q.BvXvxFgmdYsDDlPlR CSeq: 1693 INVITE Session-Expires: 1800 Min-SE: 90 Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Content-Type: application/sdp Supported: replaces, 100rel, timer, norefersub User-Agent: 3CXPhone for iOS 20.0.1.25 Content-Length: 441 v=0 o=- 3919163632 3919163632 IN IP4 10.248.72.37 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 10006 RTP/AVP 9 8 0 18 125 101 c=IN IP4 10.248.72.37 b=TIAS:96000 b=AS:117 a=rtcp:10007 a=sendrecv a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:125 opus/48000/2 a=fmtp:125 useinbandfec=1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 0 RTP/AVP 31 c=IN IP4 127.0.0.1

The working Android is assigned to a user not having 3CX Talk enabled, the iPhone to a user having 3CX Talk enabled. But maybe that is completely unrelated.

 

[AndyThe327st]

Funny. I just created a new extension as a test (103). Then provisioned it to the iPhone. It works. It can call outside and *777.

If I provision it back to my extension (100) it breaks again.

100 is also system owner. Does that make a difference?

 

[Alphabetic]

Can you check the event log from the admin page and see if theres anything there?

 

[AndyThe327st]

Yes, just set it to verbose logging and restarted to check. Before I only had those 30051 errors like the one above (Unidentified Incoming Call).

 

[AndyThe327st]

Maybe this helps to clear it up. I just revisited Accounts on the iPhone.

There is a difference between the account for extension 100 showing two different FQDN names and the new 103 test extension which shows only the external one COMPANY.ELASTIX.COM as "Server". Strange.

But when using the account that doesn't work, which does not have "Server" but "Local PBX" and "External PBX" there is a green dot near the External PBX name COMPANY.ELASTIX.COM. Seems like both accounts use the same external FQDN name.

Is it better to not use the System Owner for devices?

And the iPhone is not on the same network. The PBX is hidden in its own subnet with the Go-Box only.

 

[AndyThe327st]

I just restored the v18 and got the same problem there with the iPhone. My problems with the Gigabox have been resolved and I can call the Android from there (Gigaset) using the same account the Iphone uses.

So I don't think this is related to the v20 update but has to be something else, maybe our firewall. I got the same error now in the v18 log.

Will update later when I found it. Should have tested that earlier before wasting time on it.

 

[AndyThe327st]

I have narrowed it a bit down.

If I connect with the iPhone to v18 it shows correctly as Server and the external FQDN COMPANY.ELASTIX.COM.

I can see the iPhone in the management interface under Phones on v18.

Then I turned off the v18 and turned on the v20 again.

Then I get Local PBX COMPANY.COM / External PBX COMPANY.ELASTIX.COM again.

Any new created user works and when I provision that new user onto the same iPhone I can switch to that account without any problem and the account will not have two different FQDNs.

The INVITE has COMPANY.COM and that's probably why it won't work.

 

[AndyThe327st]

OK. I gave up. I created a new extension and renamed the old one into System Administrator. The new one provisions properly and works.