Sip T-server -> RM -> MCP

[vjicecool]

what is the good way to understand the Sip events between all three applications

3 way Sip communication is little confusing to me.

any help would be appreciated

Thanks

[cavagnaro]

Good way...tricky...not easy definitively...just sit down, study each scenario and follow the SIP messages exchange.
Basically SIP Server sends requests to RM and RM to MCP.

[vjicecool]

[quote author=cavagnaro link=topic=10447.msg47422#msg47422 date=1498495521]
Good way...tricky...not easy definitively...just sit down, study each scenario and follow the SIP messages exchange.
Basically SIP Server sends requests to RM and RM to MCP.
[/quote]

Thank you for the response and a question

does the call id generated in sip t-server for a call will remain same in RM and MCP or it will be different for each app?

[cavagnaro]

Call ID is an ID for that call, will be valid until the call exists SIP Server.

Enviado de meu E6633 usando Tapatalk

[n3vek7]

ConnId is generated by TSrv/SIPSrv,
GUID/UUID is generated by RM.

There's multiple unique key, but those two are the main one for me.

[vjicecool]

I would like to trace/troubleshoot a call

so In sip t-server i need to look for call-id and then in rm GUID and in MCP another call/guid?

is this how you usually trouble shoot or any other tool available?

[cavagnaro]

I use connid, the ANI and time of call
CallID can help too but I am not quite a fan of it

Enviado de meu E6633 usando Tapatalk

[Fra]

[quote author=vjicecool link=topic=10447.msg47465#msg47465 date=1498672606]
I would like to trace/troubleshoot a call

so In sip t-server i need to look for call-id and then in rm GUID and in MCP another call/guid?

is this how you usually trouble shoot or any other tool available?
[/quote]
If you're looking into troubleshooting SIP to GVP , I find it best through the Call-ID, as that is what is used by SIP.
ConnID for everything else.