Which two traces options can be useful when trouble-shooting SIP endpoint registration issued with a phone using TCP protocol? (Choose two.)

Question

Options

• ASIP Registration
• BTLS handshaking
• CPPM
• DCall Processing

• A
  83% (52)
• B
  11% (7)
• C
  6% (4)

Explanation

SIP Registration (A) captures the actual SIP REGISTER messages and server responses, making it the most direct trace for diagnosing why a phone fails to register. Call Processing (D) logs how the call processing subsystem handles the registration request on the server side, revealing issues like authentication failures, device configuration mismatches, or line/device not found errors - together, these two traces give you the full picture from both the client message and the server's handling of it.

TLS Handshaking (B) is a distractor because the question specifies TCP, not TLS. TLS traces apply when SIP is secured over an encrypted transport (port 5061); plain TCP (port 5060) involves no TLS negotiation, so those traces would be empty and useless.

PPM (C) (Proxy Presence Module) is related to presence and instant messaging features, not device registration - it would not surface any information about a phone failing to register.

Memory tip: Think of it as a two-layer check - "SIP Registration shows the message (what the phone sent), Call Processing shows the handling (what the server did with it)." If either layer is broken, registration fails; you need both traces to pinpoint which layer is at fault.

No community discussion yet for this question.