VoipInnovations 404 err, no route found

Identifying details anonymized. Dialing muliple 10 digit North American numbers.

I don’t think it’s the PBX since nothing was changed on it as far as I know. Previous SIP messages look like normal call negotiation until this one. The end result is an all circuits busy message.

2023/04/21 11:33:24.099039 -> xx.xx.xx.xx:5060
SIP/2.0 404 ERS:No Route Available
Via: SIP/2.0/UDP xx.xx.xx.xx:5060;branch=z9hG4bK34c063f5;rport=5060
To: <sip:[email protected]>;tag=sansay845362775rdb28095
From: "test" <sip:[email protected]>;tag=as71b725e8
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Content-Length: 0

These days, there is a good chance that From: [email protected]… will result in a rejection, although I wouldn’t expect “no route”. Depending on the provider, the From user should either be an account name, or one of the PSTN numbers allocated to you by the provider, or at least a valid PSTN number.

This was all working until today and nothing was changed on the PBX.

The law has changed, and the way that providers handle that has changed.

Inserting the CID on the outbound route seems to have worked. Was this restriction just added by VI today? I’m pretty sure they used to just replace the extension with the CID on their end.

Their configuration example does not show anything in CID Route.


This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.