?

Log in

No account? Create an account
Quite some time was spent today trying to create a test environment… - 'Twas brillig, and the slithy toves did gyre and gimble in the wabe [entries|archive|friends|userinfo]
Thomas

[ website | Beware the Jabberwock... ]
[ deviantArt | the-boggyb ]
[ FanFiction | Torkell ]
[ Tumblr | torkellr ]

Links
[Random links| BBC news | Vulture Central | Slashdot | Dangerous Prototypes | LWN | Raspberry Pi]
[Fellow blogs| a Half Empty Glass | the Broken Cube | The Music Jungle | Please remove your feet | A letter from home]
[Other haunts| Un4seen Developments | Jazz 2 Online | EmuTalk.net | Feng's shui]

[Friday 23rd November 2012 at 11:12 pm]
Thomas

boggyb
[Tags|]
[Feeling |accomplishedaccomplished]
[Playing |Sleeping Awake ~ P.O.D./The Matrix Reloaded: The Album]

Quite some time was spent today trying to create a test environment for a particularly convoluted SIP call flow (with the test harness code getting more and more twisted in an attempt to achieve it), until I had a wonderful moment when I realised that almost the entire call flow was completely irrelevant to the actual test.

The only part that mattered was a single message out of my system, and of that all I needed to know was where it was headed. And that depends on a single header in the incoming message, which only has to match reality if I need later requests/responses in the call to go to the right place. So my test suddenly became a lot easier: swap the high-level test harness out for another much more low-level one that lets you send whatever you want, craft a script to send a few INVITEs with completely bogus headers, and watch the results with a packet analyser. Success!
Link | Previous Entry | Share | Next Entry[ Penny for your thoughts? ]