Solved 480 Temporarily Unavailable with custom trunk

[yetopen]

Hi.
I'm trying to use my landline phone number as trunk for 3CX. I already did this and the setup is working, unfortunately I'm not able to replicate it to another location. The landline is a VoIP number configured on a Fritz Box router. I added an user on the modem, given external registration capabilities and works perfectly with i.e. Zoiper client, I can make calls from anywhere. With the same setup, when I configure the Fritz as trunk in 3CX I cannot make calls, I get the 480 as an answer.

I tried disabling the firewall on the 3CX server but I get the same result.

I double checked the trunk configuration on the working setup and on this one and they're the same. I tried some minor changes but no improvements.

Trunk options:


Codec priority:

1. G729
2. G.711 U-law
3. G.711 A-law

Activity log for a call from extension 00 to external number 119 (tried other more classical destinations, doesn't matter).

I'd say it's a trunk configuration but cannot tell what.
Help welcome.

Many thanks.

09/07/2020 6:42:18 PM - Stop call record for leg L:3.1[Extn:00]
09/07/2020 6:42:18 PM - Removing leg L:3.1[Extn:00]
09/07/2020 6:42:18 PM - L:3.1[Extn:00]: Terminating targets, reason:
09/07/2020 6:42:18 PM - Leg L:3.1[Extn:00] is terminated: Cause: BYE from PBX
09/07/2020 6:42:18 PM - Call(C:3), Extn:00 on exit: DlgInfo(3-1135/Terminated / I)
09/07/2020 6:42:18 PM - Call(C:3), Extn:00 on entry: DlgInfo(3-1135/Terminated / I)
09/07/2020 6:42:18 PM - Notify dialog-info: Extn:00: sip:[email protected]:5060;rinstance=0-bc36c977-25da-47ec-9805-2ad932187734, Call(C:3)
09/07/2020 6:42:18 PM - L:3.1[Extn:00] Sending: OnSendResp Send 480/INVITE from 0.0.0.0:0 tid=Pj486d0dad-be1c-49d7-8fa0-fdc5313ca376 Call-ID=7876fe86-d59d-4d12-a565-2e73d7c25e41:

SIP/2.0 480 Temporarily Unavailable

Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---Pj486d0dad-be1c-49d7-8fa0-fdc5313ca376;rport=5080

Via: SIP/2.0/UDP [::ffff:3cxclient.public.ip]:52276;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-bc36c977-25da-47ec-9805-2ad932187734_9668240

Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPj486d0dad-be1c-49d7-8fa0-fdc5313ca376;alias

To: <sip:[email protected];tag3cx=946ecbfb-f95a-46d2-8e09-a1e04c629cf6>;tag=4b1e913a

From: "yetopen"<sip:[email protected]>;tag=7f996798-7186-4c44-939d-1c1fbef51f68

Call-ID: 7876fe86-d59d-4d12-a565-2e73d7c25e41

CSeq: 29429 INVITE

Warning: 499 my3cx.domain.it "No answer"

Content-Length: 0



09/07/2020 6:42:18 PM - Call(C:3), Extn:00 on exit: DlgInfo(3-1135/Terminated / I)
09/07/2020 6:42:18 PM - Call(C:3), Extn:00 on entry: DlgInfo(3-1135/Initial / I)
09/07/2020 6:42:18 PM - Notify dialog-info: Extn:00: sip:[email protected]:5060;rinstance=0-bc36c977-25da-47ec-9805-2ad932187734, Call(C:3)
09/07/2020 6:42:18 PM - [CM503020]: Call(C:3): Normal call termination. Call originator: Extn:00. Reason: No answer
09/07/2020 6:42:18 PM - [CM503016]: Call(C:3): Attempt to reach <sip:[email protected]:0> from Extn:00 has failed. Reason: No Answer
09/07/2020 6:42:18 PM - L:3.1[Extn:00] failed to reach Line:10000>>119, reason No Answer
09/07/2020 6:42:18 PM - Call to T:Line:10000>>119@[Dev:sip:[email protected]:5060] from L:3.1[Extn:00] failed, cause: Cause: 408 Request Timeout/INVITE from local
09/07/2020 6:41:46 PM - [CM503025]: Call(C:3): Calling T:Line:10000>>119@[Dev:sip:[email protected]:5060] for L:3.1[Extn:00]
09/07/2020 6:41:46 PM - [Flow] Call(C:3): making call from L:3.1[Extn:00] to T:Line:10000>>119@[Dev:sip:[email protected]:5060]
09/07/2020 6:41:46 PM - [CM503027]: Call(C:3): From: Extn:00 ("yetopen" <sip:[email protected]:0>)  to  T:Line:10000>>119@[Dev:sip:[email protected]:5060]
09/07/2020 6:41:46 PM - [CM503004]: Call(C:3): Route 1: from L:3.1[Extn:00] to T:Line:10000>>119@[Dev:sip:[email protected]:5060]
09/07/2020 6:41:46 PM - Call(C:3): Call from Extn:00 to 119 matches outbound rule 'da via Grandi'
09/07/2020 6:41:46 PM - [Flow] Call(C:3): has built target endpoint: Out#:>>Rule{da via Grandi}>>119 for call from L:3.1[Extn:00]
09/07/2020 6:41:46 PM - [CM503010]: Call(C:3): Making route(s) from Extn:00 to <sip:[email protected]:0/UDP>
09/07/2020 6:41:46 PM - Remote SDP is set for leg L:3.1[Extn:00]
09/07/2020 6:41:46 PM - OnOffer from L:3.1[Extn:00]
09/07/2020 6:41:46 PM - [CM505001]: Endpoint Extn:00: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 16.4.3.131] PBX contact: [sip:[email protected]:5060]
09/07/2020 6:41:46 PM - [CM500002]: Call(C:3): Info on incoming INVITE from Extn:00:

Invite-IN Recv Req INVITE from 127.0.0.1:5080 tid=Pj486d0dad-be1c-49d7-8fa0-fdc5313ca376 Call-ID=7876fe86-d59d-4d12-a565-2e73d7c25e41:

INVITE sip:[email protected]:5060;transport=UDP;tag3cx=946ecbfb-f95a-46d2-8e09-a1e04c629cf6 SIP/2.0

Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---Pj486d0dad-be1c-49d7-8fa0-fdc5313ca376;rport=5080

Via: SIP/2.0/UDP [::ffff:3cxclient.public.ip]:52276;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-bc36c977-25da-47ec-9805-2ad932187734_9668240

Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPj486d0dad-be1c-49d7-8fa0-fdc5313ca376;alias

Max-Forwards: 69

Record-Route: <sip:[email protected]:5080;user=proxy;uri=clnt.0-bc36c977-25da-47ec-9805-2ad932187734_9668240>

Contact: "yetopen" <sip:[email protected]:5060;rinstance=0-bc36c977-25da-47ec-9805-2ad932187734>

To: <sip:[email protected];tag3cx=946ecbfb-f95a-46d2-8e09-a1e04c629cf6>

From: "yetopen"<sip:[email protected]>;tag=7f996798-7186-4c44-939d-1c1fbef51f68

Call-ID: 7876fe86-d59d-4d12-a565-2e73d7c25e41

CSeq: 29429 INVITE

Session-Expires: 1800

Min-SE: 90

Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS

Content-Type: application/sdp

Proxy-Authorization: Digest username="9ajnFYxvQ8",realm="3CXPhoneSystem",nonce="414d53595f5662ca89:f44e0ce770e64c66d495e812c503028f",uri="sip:[email protected];tag3cx=946ecbfb-f95a-46d2-8e09-a1e04c629cf6",response="d65c103fd3d891b897d6228f36f4424a",algorithm=MD5

Supported: replaces, 100rel, timer, norefersub

User-Agent: 3CXPhone for Android 16.4.3.131

Content-Length: 448



v=0

o=- 3808485704 3808485704 IN IP4 192.168.254.29

s=pjmedia

c=IN IP4 127.0.0.1

b=AS:84

t=0 0

a=X-nat:0

m=audio 14020 RTP/AVP 18 0 8 9 3 96

c=IN IP4 127.0.0.1

b=TIAS:64000

b=AS:84

a=sendrecv

a=rtpmap:18 G729/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:9 G722/8000

a=rtpmap:3 GSM/8000

a=rtpmap:96 telephone-event/8000

a=fmtp:96 0-15

a=ssrc:1815478776 cname:76b802e248a558f9

m=video 0 RTP/AVP 31

c=IN IP4 127.0.0.1

09/07/2020 6:41:46 PM - [CM503001]: Call(C:3): Incoming call from Extn:00 to <sip:[email protected]:0>
09/07/2020 6:41:46 PM - Leg L:3.1[Extn:00] has external party ID {}
09/07/2020 6:41:46 PM - L:3.1[Extn:00]: device's outbound URI is used: 127.0.0.1

 

[leejor]

Just so I get a clear picture of what you are trying to do... you have a VoIP service, but are not attempting to register a 3CX direct to that, instead you are trying to register to your Fritz box, which is then registered to the VoIP service? Is that about it?

 

[yetopen]

instead you are trying to register to your Fritz box, which is then registered to the VoIP service? Is that about it?

Exactly. The VoIP number is bond to that DSL line, so I cannot register from outside

 

[leejor]

So from the Fritz box, you are able to register SIP devices, as extensions (I assume?)

 

[yetopen]

So from the Fritz box, you are able to register SIP devices, as extensions (I assume?)

Yes. I have created an extension with remote registration capabilities (by default only LAN IPs are allowed for Fritz extensions). The 3CX trunk is one of these extensions

 

[leejor]

So 3CX is not on the same LAN as the FB? It's hosted?

 

[leejor]

Are you using a Generic trunk in 3CX, or a Bridge trunk?

 

[yetopen]

So 3CX is not on the same LAN as the FB? It's hosted?

3CX is on a cloud hosting, outside the LAN

Are you using a Generic trunk in 3CX, or a Bridge trunk?

It's a generic trunk

 

[leejor]

Call(C:3): Call from Extn:00 to 119 matches outbound rule 'da via Grandi'

[CM503016]: Call(C:3): Attempt to reach <sip:[email protected]:0> from Extn:00 has failed. Reason: No Answer

What call is this? Is this routing to the Fritz Box trunk?

 

[yetopen]

What call is this? Is this routing to the Fritz Box trunk?

What do you mean? It's a normal call, started from the Android app to the 119 number (call center). Yes, the only outgoing route of the 3CX goes through the Fritz (via grandi)

 

[leejor]

So the trunk called Grandi is the one to the FB?

Call to T:Line:10000>>119@[Dev:sip:[email protected]:5060] from L:3.1[Extn:00] failed, cause: Cause: 408 Request Timeout/INVITE from local

So this message suggests that you are attempting to send the call to the FB and there awas no response. Does the FB have a log (syslog?), to show the incoming call attempt? Is the trunk set to regster and showing as registered, in 3CX?

 

[yetopen]

So the trunk called Grandi is the one to the FB?

yes

So this message suggests that you are attempting to send the call to the FB and there awas no response. Does the FB have a log (syslog?), to show the incoming call attempt? Is the trunk set to regster and showing as registered, in 3CX?

I haven't found a proper log, but I can do a tcpdump. Here's the output on wireshark of an attempted call to 0341*

 

[leejor]

So is the highlighted line, the response from the FB to the Invite from 3CX?

 

[leejor]

Since the trunk is registering correctly, I have to assume the the credentials are being seen as correct. I'm wondering if it has anything to do with the caller ID that is being sent, when placing a call.
Not being familiar with the FB (other than seeing them for sale in the stores, when in Europe), I have no idea how strict they are with regards to that.

 

[leejor]

Have you tried using a bridge trunk, as you are, bridging to , what is essentially, another PBX.

 

[yetopen]

Have you tried using a bridge trunk, as you are, bridging to , what is essentially, another PBX.

You mean this configuration? On the Fritz I can create a classic user account, while the bridge slave config expects only a password.

Since the trunk is registering correctly, I have to assume the the credentials are being seen as correct. I'm wondering if it has anything to do with the caller ID that is being sent, when placing a call.

I suspect it has something to do with that, but I haven't been able to find what

 

[yetopen]

Managed to solve! Ended up you can never trust users, neither power users (that's me).

As you guessed there was something wrong with caller id. I checked again with the working configuration and found Contact and From user parts being different. After setting both to AuthID I was finally able to make calls using the Fritzbox.

Thanks for the support.