I have never played with the port option as a qualifier, and the system I have setup does not have a media gateway configured to do any testing against. Normally CM will chunk back data till the last block, at which point you will get less than the count. So if your config is small enough, test with out the port qualifier for a bit and see what behavior you see; also use the SAT terminal to see if you are seeing the same behavior with both interfaces.
Normally one would do a list station ext xxxx count, and build their own DB of the info, and refresh it every so often, and have your system work against that DB. But I can understand why that is less than desirable if you are just trying to collect what is provisioned against a certain circuit pack.
Given your example with a count of 6 (two past the total of 14) works, and a count of 7 fails (I think that is what you are conveying), I think there is something very strange going on, but I could be totally missing your point because at one point you indicated a query for the second chunk failed, and at another I infer things are working. By strange going on, my guess is that there is some station configured in a way that causes an issue with the list command at the SAT or if the SAT works, and SMS doesnt, then the problem data is an issue with SMS.
The CM connection being 'lost' is likely a timeout. Is it 100% repeatable? If so I would expect more that some configured data in CM is creating an issue for SMS. It isn't supposed to, but it isn't impossible either. If you run the commands on CM SAT are they successful? If so that would imply a SMS issue with the data it is receiving. By enabling SMS tracing and reviewing those logs, you could see if the data is arriving from CM and not making it to the app, or CM isn't sending the data. A technical support ticket would be the better mechanism to provide assistance with that assuming your company has a support-enable of higher membership.
|