UDT encoding of short size messages for the case when LMR rules allows it #191

Closed
vetss opened this Issue Jan 10, 2017 · 0 comments

Comments

Projects
None yet
2 participants
Collaborator

vetss commented Jan 10, 2017

When LMR option for a destination is XUDT_ENABLED then now all SCCP messages are encoded as XUDT. You need that in this case if a message is short enouph to avoid of segmenting then we need to encode it as UDT (not XUDT).

PS: But I have one suspition. When we play role an STP (SCCP transit) then it may occure when we receive UDT message and the next destination has longer SCCP address and a message does not fit UDT limitation then we need to switch to XUDT (if it is enabled by LMR). This does not concern a feature request, but let's think of this.

@vetss vetss added the enhancement label Jan 10, 2017

@vetss vetss added this to the 8.0.0 milestone Jan 10, 2017

@vetss vetss self-assigned this Jan 10, 2017

@knosach knosach self-assigned this Dec 12, 2017

@knosach knosach closed this in 21cd63c Dec 14, 2017

@vetss vetss changed the title from UUDT encoding of short size messages for the case when LMR rules allows it to UDT encoding of short size messages for the case when LMR rules allows it Dec 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment