« SIP and AMR | Main | I Can Now Detect over 25 Wifi Networks At My Flat! »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83451c34f69e2010534d95234970c

Listed below are links to weblogs that reference An IMS Wireshark Trace:

Comments

vingarzan

No need to ask for permission on traces, because the project is anyway Open Source and experimentation is its main goal.

Because Wireshark is a great tool, I feel that I should make some comments. First of all, the xml AVP definition files get added all the time to the default Wireshark configurations. It just takes some time.

I remember that when we started to implement the first Diameter interfaces of the Open IMS Core(around 2004, I guess) there were some typos in there, like the Cx id being 167772151. Now as a geek, one immediately sees that 16777215 and 16777216 are too nicely chosen, so there must've been a typo. And there was, in one of the 29.228 or 29.229. Looks like they wanted to say 16777215 +1,+2, etc but some spell-checking secretary at ETSI knew better ;-). This was corrected soon enough, but for a while you had to fix the Wireshark definitions (or not fix them as others really implemented it with the wrong id :-p).

Then about ports 4868 and 5868 - 3868 still stays the only standardly defined port for Diameter. It's just that we use different ports because we run all those Diameter components on just 1 system. We also use for example ports 3869 and 3870 for the I and S-CSCF traffic, 3868 being usually the HSS. Now because your Diameter connection could happen in both directions, you could see the Diameter traffic with the source or destination on any of the ports in the list.

Cheers,
-Dragos

The comments to this entry are closed.

My Photo

The Books to this Blog

Secure Hotel Wi-Fi Sharing

My Pictures on Flickr

  • www.flickr.com
    martin.sauter's photos More of martin.sauter's photos

Misc

  • Clicky
    Clicky Web Analytics