New VMs not seeing destinations

Status
Not open for further replies.
R

rjwair

New Member
Sep 16, 2021
7
0
1
40
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?
 
So do you have an inbound route for +16603385111?

Look at the log in fs_cli it should help you more.
 
Yes I do, both destination and inbound routes.
 

Attachments

  • Capture.PNG
    Capture.PNG
    38.1 KB · Views: 5
Think you might want an optional plus in there to handle E164:

^\+?(0123456789)$
 
Also, no need for you to touch inbound routes generally, the destination should do it for you.
 
hfoster said:
Think you might want an optional plus in there to handle E164:

^\+?(0123456789)$
Click to expand...
Ok this fixed it, but why are my instances auto formatting it at ^( instead of automatically adding and imply ^\+?( when I create the destination?
 
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:

signalwire.com

FusionPBX

Real-time communication & collaboration platform. SignalWire - Connect, Engage, Innovate. Trusted by thousands. Get started today.
signalwire.com signalwire.com
 
Status
Not open for further replies.
Top Bottom