I'm needing to find a way to see the raw XML getting sent to the phone. Does anyone know of a way that allows me to (a) debug the screen such that I see the text getting sent to it, or (b) essentially span the third port of the phone so I can sniff packets the phone sends to itself?
Run a packet sniffer on the PC that is daisy-chained off the phone. The 'switch' inside the phone actually behaves more like a hub and all of the traffic to/from the phone is present on the computer network connection. Even if the phone traffic is assigned to a different vlan, it shows up on the computer port without any vlan tagging. This includes broadcast traffic on the phone vlan.
Thanks for the reply. I can launch a sniffer and see packets between the phone and Call Manager (or between the phone and my PC or between the phone and some other device, etc.). What I can't see, though, are packets that the phone sends to itself, such as the xml displayed on the screen of the phone after pressing the "settings" button. Any magic way you know of to make that happen?
I do not agree with this. I have a sniffer running on my PC which is attached to an IP phone, and the only traffic I see is on the "Data" VLAN. No packets from the "Voice" VLAN are making their way to my PC, including broadcasts.
I dunno; you might try making certain that your sniffer is running in promisuous mode (which rules out Network Monitor). I've always just seen them; and in fact I see packets from my host twice; I presume once as the packet leaves my NIC and again when it leaves the phone toward the switch.
None of this, though, was the point of my original post. What I'm needing to do is sniff packets that stay internal to the phone, when you browse the Settings button for example. An alternative is the ability to run debugs on xml post events, etc. like the ones that are available the SIP version.
Anyone know of a way to run basic debugging or gain console access to phones running Skinny code versions?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...