New VMs not seeing destinations

[rjwair]

I use signal wire as my provider, and on my new VM install on both ubuntu server 20.04 and Debian 11 I get an issue that even after I've added all the address from dig sip.signalwire.com to cidr in provider, added and reged gateway, added extension, and added destination I still get 404 NO_ROUTE_DESTINATION when looking at sngrep. Anyone offer any guidance on this?

 

[rjwair]

 

[DigitalDaz]

So do you have an inbound route for +16603385111?

Look at the log in fs_cli it should help you more.

 

[rjwair]

Yes I do, both destination and inbound routes.

 

[hfoster]

Think you might want an optional plus in there to handle E164:

^\+?(0123456789)$

 

[DigitalDaz]

Also, no need for you to touch inbound routes generally, the destination should do it for you.

 

[rjwair]

Also, no need for you to touch inbound routes generally, the destination should do it for you.

I have my destination in, it still 404 when inbound.

 

[rjwair]

Think you might want an optional plus in there to handle E164:

^\+?(0123456789)$

Ok this fixed it, but why are my instances auto formatting it at ^( instead of automatically adding and imply ^\+?( when I create the destination?

 

[hfoster]

Yeh, I suppose that could be a pull-request in the destination page. It's weird that SignalWire's guide doesn't pick up on it either:

FusionPBX

Real-time communication & collaboration platform. SignalWire - Connect, Engage, Innovate. Trusted by thousands. Get started today.

signalwire.com