-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error "missing Origin-State-Id" whilst using diam/sm. #42
Comments
missing Origin-State-Id
whilst using diam/sm
.
Sounds like the error you get is because the server you're connecting to does not respond with a CEA containing |
@fiorix You're absolutely correct. It's sending back an error message (3099).
Might it be worthwhile to override the CER within the state machine's |
@fiorix Curiously, the only way I've managed to get a valid CEA response thus far has been to completely remove the FirmwareRevision AVP. https://github.com/fiorix/go-diameter/blob/master/diam/sm/client.go#L179 Would you be open to swapping out that line for the following, which also appears to work? |
I see, the |
Closing this in favor of #44. |
@fiorix Would you mind reopening this as it's not quite a fit with #44. It turns out the CEA truly doesn't include the |
Sure |
Could you please try this dev branch? |
Attempting to use state machine in a similar fashion as the
client.go
example, results in an error,missing Origin-State-Id
. There's no clear way to update the handshake CER with the AVP in question in the case that it is indeed missing. A snippet from the application is below:The text was updated successfully, but these errors were encountered: