Failed Registration with status Operation has no matching challenge [904].

[jamesc]

Hi,

I've been evaluating various multi-tenanted PBX solutions recently, and FusionPBX/Freeswitch seems a nice solution. However I am running into issues that I'm sure are simple to fix, just I'm unsure how! I do seem to keep hitting a bug where I end up with "phantom" gateways that I then have to manually delete (this seems to happen if changing sip profile).

I am simply unable to get it to register with our SIP trunk provider. I've set the sip proxy, the sip username and the sip password correctly, I've tried adding the username to auth-username, I've tried setting the proxies all to the sip trunk address, but I keep getting this error:

2019-12-31 15:44:02.863202 [ERR] sofia_reg.c:2469 6459025e-8006-4195-8c70-37ee7f2e7e03 Failed Registration with status Operation has no matching challenge [904]. failure #4

In fs_cli with loglevel 9 I'm seeing messages such as:

nta.c:3299 agent_recv_response() nta: received 401 Unauthorized for REGISTER (14349790)
nta.c:3366 agent_recv_response() nta: 401 Unauthorized is going to a transaction
nta.c:9602 outgoing_duplicate() nta: 401 Unauthorized is duplicate response to 14349790 REGISTER

and I'm at a loss as to what the next step might be. I'm reluctant to believe that the sip trunk provider is simply incompatible with Fusion PBX.

Thanks

 

[Adrian Fretwell]

We had something similar to this a few years ago with another UAS (Not FreeSwitch) It was a badly constructed www-Authenticate header in the 401 message. If you can get a packet capture of the registration message exchange it may shed a little more light on what is going on.

I've never seen "phantom" gateways appearing - no idea what is going on there.

 

[jamesc]

Thanks for replying, using your pointers I used sngrep to work out it was a DNS issue and Fusion seems registered, and stable