-
Notifications
You must be signed in to change notification settings - Fork 227
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
ISUP: Update messages in accordance with ITU Q.763 #201
Comments
Hello @agafox thank you for opening an issue. Feel free to provide update for ISUP messages if you mean it is needed. We will include it into sources. |
Hello @vetss I've reviewed all ISUP messages. Only AIM is not up to date with ITU Q.763 2 of this parameters not implemented in jss7 at all:
I suggest to update IAM with 23 implemented in jss7 parameters and create new issue to implement parameters above because now I'm not sure I have enough time to do it (Calling geodetic location - very complex parameter...) |
Hello @agafox ok, let's start with what we have. Feel free to provide a PR to the staff you can cover. |
Thanks @vetss Let's close this issue, because I have no time to implement missed parameters in February and March. I believe I'll come with pull request in future. |
I am closing the issue now. Feel free to open a new one for finishing the work |
In my project I found ISUP IAM messages with optional parameters from Q.763 (for instance, 'Called IN number', 'UID capability indicators', e.t.c) which don't defined in 'InitialAddressMessage' object.
So, any attempt to decode such messages leads to Exception.
I could try to review ISUP messages and update them in accordance with Q.763
The text was updated successfully, but these errors were encountered: