@dicko Thanks for your speedy reply. In addition to one Anveo DID, I have two VoIP.ms DIDs. Suppose we say the Anveo DID is 604-999-1111, and the two VoIP.ms DIDs are 604-999-1112 and 604-999-1113. FYI, I can make calls to the two VoIP DIDs without any problems.
Until a few minutes ago the Inbound Routes Table looked like this:
DID CID Description Destination
6049991111 Any Incoming-604-999-1111 Extensions:1001
6049991112 Any Incoming-604-999-1112 Extensions:1002
6049991113 Any Incoming-604-999-1113 Extensions:1003
The error message I received was
Call from <ANVEO-SUB-ACCOUNT> 67.212.84.21:XXXX to extension <6049991111> rejected because extension not found in context from-anveo
Now, after reading your suggestion, I added a line to Inbound Routes as follows:
DID CID Description Destination
Any 6049991111 from-anveo Extensions:1001
6049991111 Any Incoming-604-999-1111 Extensions:1001
6049991112 Any Incoming-604-999-1112 Extensions:1002
6049991113 Any Incoming-604-999-1113 Extensions:1003
I’m still getting the identical error message:The error message I received was
Call from <ANVEO-SUB-ACCOUNT> 67.212.84.21:XXXX to extension <6049991111> rejected because extension not found in context from-anveo
@dicko Problem solved. In PEER Details I changed “context:from-anveo” to “context:from-trunk” and calls are going through now when I call the Anveo DID. context:from-trunk is the entry that works for the VoIP.ms DIDs.
FYI, I had used “context:from-anveo” because that is what the Anveo web page recommended for “Asterisk”.
In any case, thanks for your help. You’ve helped me more than once and it’s appreciated.