atcomsystems.ca/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems Samsung Wireshark Captures

Hi guys, please can someone help me as I have some issues that will not go away.
I don't want to write war and peace site history and too much info, but has anyone else run Wireshark captures with Samsung MGI16 or OAS cards during an IP2IP call or a IP2TDM call ?.

Basically what I find strange is that IP2IP capture seem normal but when I make any IP2TDM call I see lots of strange fragmented packets to seemingly random public IP's (the source and destination are public IP's) with no fixed sequence of these addresses.

Within Wireshark these packets with these public IP's seem to have 2 IP protocol fields with one set public (source and destination) and one set private.
Not sure I can post pics or links to the actual captures that I have available ?.
but I badly need help with this !.

Samsung 7200 (MCP Card)
SW version 4.14k
MGI16 with FW 1.20

Thanks in advance and you can PM for further info.
Please help !!!.

Holy kissing of the Blarney Stone by a snake that has been killed by St. Patrick himself.

4.14 software is so old I am surprised any of your IP is working.

The is a procedure for swapping files to get the card up to 4.30 then the Samsung site to use IT Tools to get it up to current software. Why you can't go directly to IT Tools I don't know I am just told you can't.

An even easier way would be to buy a new MMC card, input all the programming and then use the old card to learn how to upgrade software without risking the current database before the customer is up.

All 4.xx software releases for OS7000 use IT Tool.

4.14 on OS7200 MCP was the last version which had PCMMC (Officeserv Manager) though it had a bug with ring plan times.

You can go strait from 4.14 to 4.30 (ive done it with no issues on OS7100).

In wireshark make sure you go into the preferences and change the PCLI port to 0 (it defaults to 9000 which is what ITP phones use), and tick try to decode RTP outside.

Where are the ITP phones located? public or local?

Hi guys.
The ITP phones are working across a LAN-LAN VPN (so no need to port forwarding as all private addressing/routing) maintained by the customers IT provider.
We brought a few IP phones to test from the local network last week and when making IP2TDM calls to digital phones, pstn or VM we saw allo sorts of traffic to seemingly random IP's (not multicast addresses)within the Wireshark captures.
Just wondering if anyone has seen this or has any actual experience of this ?, to me this does not seem normal that on a call of this nature there would be any public addressing (well as mentioned in previous post packet has 2 IP fields).

History of issues on the site over several months, initially these phones were working Public (NAT working) but the phones started losing registration and doing funny things but the quality was totally fine, when this problem happened it was a reboot of main site router to resolve.
After a meeting with the IT firm we agreed to the traffic to the VPN (as this was not originally in place) and to my surprise as soon as we changed to VPN traffic the quality dropped off dramatically and we still have phone registration timeouts and signalling errors, again it's a reboot of main site router to cure handset registration issues but quality is poor even after changing codec to G729.

We have been advised to upgrade the MGI FW to 1.26
but need the rom chip upgraded first and there are issues around with hardware.

Any advice ?.

Hey Nameless,
Great tip on the PCLI port, suddenly my traffic looks normal and I can see the RTP info and all private normal looking packets.
I was convinced the traffic that I was seeing was actually the MGI card trying to route out to actual public IP's.
Have been very focused on the results of those strange packets and blaming our kit for this generating this strange traffic, maybe have lost sight of the fact that it was something in Wireshark preferences.

Any further advice ?.

Send me the capture file and I'll see if I can make any sense of it.
TekMason

PM sent TekMason

Since the phones are on a Private IP range, have you set the MP/MGI back to private only?

Or put the broadcast range (eg 192.168.1.255) of the remote subnet into the Private IP List MMC?

Nameless,
The site also has SIP trunks as well so under MGI setup we have used Public with Private setup and LAN setup is Private Only (Didn't want to mention MMC's as per site rules).
Can you PM me the MMC for the correct setup of the Private list ?.
Example
Main site is 192.168.0.XXX (System and MGI LAN)
Remote site 1 - 3 x IP phones 192.168.41.XXX
Remote site 2 - 1 x IP Phone 192.168.88.XXX

Thanks
Al

pm sent