has one username:
has 3 username
ll great information but mostly useless to trouble shoot your issue remotely…
Cant compare SUSCRIBE and NOTIFY for ERROR with provided logs. Log OK/OK does not have that information, BAD/OK does.
username3,4,5 in BAD/OK ,ONLY 3 in OK/OK
I’m not trying to be mean Required information is missing.
How I would gather 1st log.
1 Setup syslog server
2. Configure device to send logs to syslog server.
3. Power off device.
4 Ensure no GUI WebUI access of device during testing
5. Contact Vendor
6. Request Tech Support\
- Request a L2+ Tier tech for LIVE TROUBLE SHOOTING,
- Prepare the Tech Support Agent for a LIVE SIP CAPTURE.
- Power on device.
- Place 1st inbound call.
- Answer call on device
- Place 2nd inbound call
- Put 1st on hold Answer 2nd call.
- Join calls.
- Hang up
- Get SIP trace from tech via email or similar.
- Say Thank you!!.
7 Go have a 1++ beers, mumble about how this is stupid and this sh!t should just fuqn work!!
You have a clean log of a device contacting VENDOR and OK INCOMMING call, another incoming call, 1 call on hold and then 2 calls joined together and a hang-up
Thad’s only half of the information needed to remotely understand WTF is going on (3 usernames ?)
You estimated 12 hours before error?
Reboot device so that error will occur approximately 12 hours later and convenient for you to trouble shoot,
Make inbound calls until ERROR occurs about an hour before expected time.
Clean up the beer you just spilled getting excited about being right regarding the 12 hour thing
Place new syslog with other 2 files
IVE BEEN CALLING FOR 4 HOURS AFTER IT USUALLY HAPPENS AND IT STILL WORKS!!
That tells us that inbound calls do something (reset a timer somewhere) that keeps it working and IDLE makes it break.
Drink the last beer from yesterday leave and, get more on the way home…It’s about 12 hours until you get any more data.
With device in FAILED INBOUND ERROR refer to beginning of this post and how to get a log from VENDOR of failed inbound call while you get a log file from your side.
You should now have the following log files (more is fine)
Device power on and inbound test.
Vendor log from power on and inbound test
Inbound BAD your files
Inbound Bad VENDOR files.
problem will be in that data and you, I or the vendor or a savior will find it.