Outgoing call issue [nobody@IP]

A

alexsc

New Member
Nov 13, 2025
4
0
1
37
Hi All,
Thanks for all your help so far, this forum has been a great help to get our PBX setup...well almost setup!

Our incoming call are working great, connecting to our Yealink SIP-T57W phones with no audio issues.
For outbound calls however, the calls aren't going through and can't get past the PBX to connect to our gateway.
I have posted the error below, my thinking is that it has something to do with the username registering as nobody@IP but I can't find anywhere where this is being set.
For incoming calls the extension/username is correctly showing as 100, however on outbound showing as nobody.
Your help to resolve is greatly appreciated!

Our PBX is on a separate network to our IP phones. Both networks are behind pfsense firewalls.
Let me know if you need anymore information.



Code: 
fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:41.422255 94.63% [NOTICE] switch_channel.c:1142 New Channel sofia/internal/nobody@[client-public-ip]:65006 [fba8bd56-c205-4ef4-8e7a-cbce180611d9]

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:41.422255 94.63% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/nobody@[client-public-ip]:65006) Running State Change CS_NEW (Cur 1 Tot 46)

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:41.422255 94.63% [INFO] sofia.c:10460 sofia/internal/nobody@[client-public-ip]:65006 receiving invite from [client-public-ip]:35765 version: 1.10.12-release git 5f2f7d1 2025-11-04 19:06:03Z 64bit call-id: 16_1381393509@192.168.11.20

2025-11-13 21:58:41.422255 94.63% [DEBUG] sofia.c:10554 verifying acl "providers" for ip/port [client-public-ip]:0.

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:41.422255 94.63% [DEBUG] switch_core_state_machine.c:600 (sofia/internal/nobody@[client-public-ip]:65006) State NEW

2025-11-13 21:58:41.422255 94.63% [DEBUG] sofia.c:2419 detaching session fba8bd56-c205-4ef4-8e7a-cbce180611d9

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [WARNING] switch_core_state_machine.c:684 fba8bd56-c205-4ef4-8e7a-cbce180611d9 sofia/internal/nobody@[client-public-ip]:65006 Abandoned

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [NOTICE] switch_core_state_machine.c:687 Hangup sofia/internal/nobody@[client-public-ip]:65006 [CS_NEW] [WRONG_CALL_STATE]

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/nobody@[client-public-ip]:65006) Running State Change CS_HANGUP (Cur 1 Tot 46)

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:844 (sofia/internal/nobody@[client-public-ip]:65006) Callstate Change DOWN -> HANGUP

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/nobody@[client-public-ip]:65006) State HANGUP

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] mod_sofia.c:469 Channel sofia/internal/nobody@[client-public-ip]:65006 hanging up, cause: WRONG_CALL_STATE

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:59 sofia/internal/nobody@[client-public-ip]:65006 Standard HANGUP, cause: WRONG_CALL_STATE

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/nobody@[client-public-ip]:65006) State HANGUP going to sleep

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:616 (sofia/internal/nobody@[client-public-ip]:65006) State Change CS_HANGUP -> CS_REPORTING

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/nobody@[client-public-ip]:65006) Running State Change CS_REPORTING (Cur 1 Tot 46)

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/nobody@[client-public-ip]:65006) State REPORTING

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:168 sofia/internal/nobody@[client-public-ip]:65006 Standard REPORTING, cause: WRONG_CALL_STATE

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/nobody@[client-public-ip]:65006) State REPORTING going to sleep

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:607 (sofia/internal/nobody@[client-public-ip]:65006) State Change CS_REPORTING -> CS_DESTROY

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_session.c:1748 Session 46 (sofia/internal/nobody@[client-public-ip]:65006) Locked, Waiting on external entities

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [NOTICE] switch_core_session.c:1766 Session 46 (sofia/internal/nobody@[client-public-ip]:65006) Ended

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [NOTICE] switch_core_session.c:1770 Close Channel sofia/internal/nobody@[client-public-ip]:65006 [CS_DESTROY]

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:735 (sofia/internal/nobody@[client-public-ip]:65006) Running State Change CS_DESTROY (Cur 0 Tot 46)

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/nobody@[client-public-ip]:65006) State DESTROY

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] mod_sofia.c:380 sofia/internal/nobody@[client-public-ip]:65006 SOFIA DESTROY

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:175 sofia/internal/nobody@[client-public-ip]:65006 Standard DESTROY

fba8bd56-c205-4ef4-8e7a-cbce180611d9 2025-11-13 21:58:51.442238 94.87% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/nobody@[client-public-ip]:65006) State DESTROY going to sleep
 
Never seen that before, is that coming from the Yealink? You can tell with 'sngrep' on the FusionPBX and looking at an INVITE. We have similar issues when a phone is configured to send INVITEs to a PBX, but they aren't REGISTERED.

The nobody username does pop up in mod_sofia when a username is not specified.
 
I've just checked with sngrep and it looks like the issue is with the Yealink.
The invite is coming from just the IP address, with no username:
14 INVITE 115.xxx.xxx.xx:22500

The phone status is showing as Registered, and "Register Name" and "Username" as 100 which is the extension.
I've also tried changing the username to 100@domain-name which also comes up with a blank username.

At least I know it will likely be a phone setting, will keep digging!
 
Might also seem obvious too, but make sure the firmware is latest. I've had a a handful of SIP related Yealink issues over the years.

Also, it's possible a SIP ALG is stripping it. You can confirm that with a packet capture from the Yealink itself.
 
Checked the packet capture and the username isn't there so doesn't look like the router is stripping it.
Will try the firmware upgrade now.

Via: SIP/2.0/UDP 192.168.11.20:5060;branch=z9hG4bK1d43718737218c3177b8b
From: <sip:192.168.11.20>;tag=1783437882
Contact: <sip:192.168.11.20:5060>
 
The new firmware has fixed the issue, checked the settings and couldn't find anything that by default looked different....very strange!!
Appreciate your help!
 
You must log in or register to reply here.
Top Bottom