SIP Trunk calling itself

[Brotto Jr]

Hi Guys,

Any help would be very appreciate.

For more then one year my project is running properly on 3CX.

But after I updated 3CX to last version fews days ago (Google Cloud server) the project is facing issues.

The issue is that FXO gateway (wich is a SIP Trunk on 3cx) is calling itself like 10 times per day.

Looking to log below it seems it is related to "07/13/2019 9:38:09 PM - Updating device Dev...", once 1 sec after that the call is in place ('07/13/2019 9:38:10 PM - Call from...')

Log:

07/13/2019 9:38:10 PM - [CM503012]: Inbound specific hours rule (unnamed) for 10004 forwards to DN:8005
07/13/2019 9:38:10 PM - [Flow] Looking for inbound target: called=10004; caller="Portaria_2012" <sip:10004@:5060>
07/13/2019 9:38:10 PM - CallerNameAddr: "Portaria_2012"<sip:10004;nf=e>
07/13/2019 9:38:10 PM - No inbound caller ID reformat rule for DN:10004 is defined, or it is disabled (<Rules />)
07/13/2019 9:38:10 PM - Line 10004 has been updated from DB
07/13/2019 9:38:10 PM - Failed to add outbound CID reformating rule for DN:10004: <Rules />
07/13/2019 9:38:10 PM - Failed to add outbound CID reformating rule for DN:10004: <Rules />
07/13/2019 9:38:10 PM - Source is identified as trunk Lc:10004(@2012_Interfone_SPA3102[<sip:[email protected]:5068>])
07/13/2019 9:38:10 PM - IncomingCall: C:98 from <sip:[email protected]:5060> to <sip:[email protected]:5060>
07/13/2019 9:38:10 PM - Added leg L:C:98.1[No endpoint yet]
07/13/2019 9:38:10 PM - Call from "Portaria_2012"<sip:[email protected]>;tag=ad8d11ce554365c4o1 to <sip:[email protected]>;tag=4cbccf63
07/13/2019 9:38:10 PM - Source is identified as trunk Lc:10004(@2012_Interfone_SPA3102[<sip:[email protected]:5068>])
07/13/2019 9:38:10 PM - Source is identified as trunk Lc:10004(@2012_Interfone_SPA3102[<sip:[email protected]:5068>])
07/13/2019 9:38:10 PM - Default best-route IP is determined as 10.128.0.2
07/13/2019 9:38:09 PM - Dev(750459926):[sip:[email protected]:5068 / 10004]: PBX contact is public IP: <sip:[email protected]:5060>
07/13/2019 9:38:09 PM - Dev(750459926):[sip:[email protected]:5068 / 10004]: Outbound is set to source: <sip:[email protected]:5068>
07/13/2019 9:38:09 PM - Updating device Dev(750459926):[sip:[email protected]:5068 / 10004] by message: DevUpd Recv Req REGISTER from 189.112.63.34:5068 tid=-a8d4dab4 [email protected]:
REGISTER sip:123.123.123.123 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.125:5068;branch=z9hG4bK-a8d4dab4;received=189.112.63.34
Max-Forwards: 70
Contact: Portaria_2012 <sip:[email protected]:5068>;expires=1700
To: Portaria_2012 <sip:[email protected]>
From: "Portaria_2012"<sip:[email protected]>;tag=7d7834578e9b32f9o1
Call-ID: [email protected]
CSeq: 56116 REGISTER
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Proxy-Authorization: Digest username="10004",realm="3CXPhoneSystem",nonce="414d53595d2a797196:71d4477115351c612f211a9cb0df9edc",uri="sip:123.123.123.123",algorithm=MD5,response="90635b528e97670fbdbcaf0ad5faa8ed"
Supported: x-sipura, replaces
User-Agent: Linksys/SPA3102-5.2.13(GW002)
Content-Length: 0
07/13/2019 9:38:09 PM - Line 10004 got Device: Dev(750459926):[sip:[email protected]:5068 / 10004]
07/13/2019 9:38:09 PM - Source is identified as trunk Lc:10004(@2012_Interfone_SPA3102[<sip:[email protected]:5068>])
07/13/2019 9:38:09 PM - Source is identified as trunk Lc:10004(@2012_Interfone_SPA3102[<sip:[email protected]:5068>])

Many Tks

 

[AWS2P]

I use some SPA3102 with V16 SP2 and never got this . surely something misconfigured or lost during update

 

[Brotto Jr]

Hi @aws2p ,

Thank for your information.

@aws2p, do you mind sharing the config of your SPA3102? I use just FXO for receving calls.

I have been using SPA3102 for than one year with no issues at all. But last week I decide upgrade SBC (raspian) and I got these random 'phantom' calls from Trunk SPA3102.

Note that SPA3102 is not pointing to SBC (it pontis to google server) and it is used just for receiving calls (the call are forward to 3cx as a sip trunk).

I dont know how or why SBC upgrade is affecting SPA3102.

I reaaly dont know what to do... any help will bee very appreciate.

Rgs

 

[AWS2P]

Sorry Brotto,
I'm not sure at all my settings may help you because my use is not the same as yours. I'm French so all regional settings are for France.

i've never used SPA3102 with cloud server, all mine are with on premise PBX.

Like you of course know , SPA3102 is an old Linksys device totally unsupported from 3CX and your speccfic way of use is perhaps hardest or may be impossible to solve.

 

[leejor]

A bit more information about the set-up. I see a number of IP's, including local IP's, in the log. Which one is the IP for the 3102? Is the 3102 using port 5068? Is the 3102, behind a router, at the same location where the SBC is located? I assume it is set to use STUN? You mention what seems to be a 3CX update, then later an SBC update, was it both? If you remove the SBC temporarily, does this behaviour continue? Has the Line 1 portion of the 3102 been disabled?

Have you made use of the Syslog built into the 3102? Even the status page will show the last calls placed/received, and may provide some clues as to what is happening.

You say it's calling itself, you mean 10004? That is to be expected, as the 3102 should be setup to "forward" incoming calls to the trunk number in 3CX. 3CX then routes the call to a destination using the trunk rules (forwards to 8005). Is it the fact it's happening 10 times a day, with no caller on the line?