Dialing one extension, getting another

End user is reporting that when incoming caller is dialing her extension, it’s going to the next extension.
So when incoming caller is dialing 203, it’s sending the call to 204.

I looked at the asterisk log file for the time, and I found this…

[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@sub-presencestate-display:1] Goto(“PJSIP/203-000011a5”, “state-,1”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Goto (sub-presencestate-display,state-,1)
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [state-@sub-presencestate-display:1] Set(“PJSIP/203-000011a5”, “PRESENCESTATE_DISPLAY=”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [state-@sub-presencestate-display:2] Return(“PJSIP/203-000011a5”, “”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dial-one:40] Set(“PJSIP/203-000011a5”, “CONNECTEDLINE(name,i)=Julie”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dial-one:41] Set(“PJSIP/203-000011a5”, “CONNECTEDLINE(num)=204”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dial-one:42] Set(“PJSIP/203-000011a5”, “D_OPTIONS=TtrI”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dial-one:43] Macro(“PJSIP/203-000011a5”, “dialout-one-predial-hook,”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dialout-one-predial-hook:1] MacroExit(“PJSIP/203-000011a5”, “”) in new stack
[2015-09-14 10:04:40] VERBOSE[15554][C-000007c3] pbx.c: Executing [s@macro-dial-one:44] Dial(“PJSIP/203-000011a5”, “PJSIP/204/sip:[email protected]:1027,15,TtrI”) in new stack

Asterisk (Ver. 13.4.0)
FreePBX 12.0.74

If there is something else I can provide to help fix this, please let me know. This was the only instance in the log file that showed the extensions that seem to be getting mixed up for the appropriate timeframe.

This looks to me like 203 is dialing 204.

Are you able to replicate the issue?

If you want to PM me the log file I could take a look at it in a few hours (pastebin or private hosting probably?)