This means I have spent a fair bit of time having to get traces out of systems to try and find out why SIP is not working. I will come back to identifying the problems in later posts, but first of all you need to retrieve the SIP trace.
On a v4 or v5 5000 you can do the following.
- In Mitel DB Programming, go to 'View' and turn on Online Monitor.
- Navigate in the left hand pane to System \ Devices and feature codes \ Sip Peers
- In the General Configuration set the SIP Message output format to 'Full'
- Set the SIP log level to 'Information'
The effect of this will be to output the SIP signalling to the systems SIP logs.
To View the logs
- Go to the Mitel System Administration & Diagnostics front end.
- At the top right click on 'Connect'
- In the panel below that, when the play button appears click on it.
- On the Favourites tab, or on the System Information tab find the 'View system logs' button in the 'System Information' box and click on it.
- The system retrieves a full list of system logs. There is a refresh button that reloads the list at any time. find the SIP section.
- The logs are quickly overwritten so check the timestamp on the logs before saving or opening the log to see if it will contain your test call.
Have Fun
John Rogers
What is an outstanding post! “I’ll be back” (to read more of your content). Thanks for the nudge! sip trunk
ReplyDelete