08-23-2024 08:59 PM
hi experts,
We have 4 CUBE that connect to different SIP trunk provider. We don't have documentation on what DID range terminate to each CUBE trunk. There is no configuration note on CUBE on what circuit number and DID, also we can't trust the dial-peer config on CUBE.
Call diagram is: PSTN--- CUBE ----UCM ---- Phones
Any suggestions easy way to check and tool to use to know the DID ranges that coming to each CUBE and map out all call flow.
I have used RTMT "Real Time Data" but not very helpful, also run debug on each CUBE but takes lot of time as have to do manay days.
Any advice?
Thanks,
K
Solved! Go to Solution.
08-24-2024 11:53 PM - edited 08-25-2024 12:11 AM
maybe this helps >>
do SSH to your CUBE >> and enable this debug >> "debug ccsip messages"
(also enable "terminal monitor" command)
and then make call to your "sip lines" one by one,
now you must see sip packets coming into your router & the "DID" (Called Party Numbers) of lines must be seen on this packets..
08-25-2024 01:34 AM
This would not IMHO satisfy the OP ask. She/he/it already wrote that doing debugs takes to much time “also run debug on each CUBE but takes lot of time as have to do manay days”. For the most we all probably know that this is what it is going to take, but it’s not really an easy thing and that’s what the OP asked for. The sort of easy thing to do is to communicate with the service providers and have them tell you what DID numbers you have on each circuit.
08-23-2024 11:37 PM - edited 08-26-2024 07:30 AM
Other than asking your service providers there are no easy way to map down what you're asking about. There isn’t any command or debug that can easily reveal this information for you.
08-24-2024 11:53 PM - edited 08-25-2024 12:11 AM
maybe this helps >>
do SSH to your CUBE >> and enable this debug >> "debug ccsip messages"
(also enable "terminal monitor" command)
and then make call to your "sip lines" one by one,
now you must see sip packets coming into your router & the "DID" (Called Party Numbers) of lines must be seen on this packets..
08-25-2024 01:34 AM
This would not IMHO satisfy the OP ask. She/he/it already wrote that doing debugs takes to much time “also run debug on each CUBE but takes lot of time as have to do manay days”. For the most we all probably know that this is what it is going to take, but it’s not really an easy thing and that’s what the OP asked for. The sort of easy thing to do is to communicate with the service providers and have them tell you what DID numbers you have on each circuit.
08-25-2024 07:15 PM
Thanks Roger and Moh Reza,
Does enable "debug cssip message" safe things to do for busy CUBE ?
Has anyone use RTMT to get the DID?
Thanks.
K
08-25-2024 09:55 PM
Yes it’s safe to enable that debug on a busy system.
08-25-2024 10:19 PM - edited 08-25-2024 10:20 PM
as dear @Roger Kallberg said
it's safe to use..
before of it
enter this command >> "terminal monitor"
and also don't forget to disable it
after finishing your examination
by entering this command >> "undebug all"
08-26-2024 07:25 AM
Thanks both,
Since we are busy, I heard using syslog will be better to capture for 1 week. And best practice steps how to?
Rgds
K
08-25-2024 10:24 PM
because your entry point is the "CUBE"
and you have it
it's provide very great debug to enable & use, for finding out what's happening in depth of sip calls ?..
08-25-2024 02:54 AM
dear @Roger Kallberg
yes, of course..
you are right ^-^
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide