Hi!
I have a phone (Mitel 6930) that does not send an Expire-header but "expire" in Contact during REGISTER:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:pbx.example.com SIP/2.0 Message Header Via: SIP/2.0/TLS 192.168.6.16:5061;branch=xxxxxxxxxxxxxxxx;rport Route: <sip:pbx.example.com;lr=lr;transport=tls> Max-Forwards: 70 From: "Example" <sip:121212_6666@pbx.example.com>;tag=b0cec92c3e To: "Example" <sip:121212_6666@pbx.example.com> Call-ID: aaaaaaaaaaaaaaaaa CSeq: 1190442896 REGISTER Accept-Language: de Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE,PRACK, SUBSCRIBE, INFO, PUBLISH Allow-Events: talk, hold, conference, LocalModeStatus Contact: "Example" <sip:121212_6666@192.0.2.1:62336
;+sip.instance="urn:uuid:00000000-0000-1000-8000-08000FB888F5";expires=300
Supported: path, gruu User-Agent: Mitel 6930/5.0.0.2041 Aastra-Line: 1 Aastra-Mac: AAAAAAAAAAAA Content-Length: 0
This results in successful register, kamailio forwards REGISTER to asterisk (endpoint registered) and immediatly kamailio sends a new REGISTER with Expire set to 0 to asterisk:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:192.168.99.112:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.99.111:5060;branch=z9hG4bK9f9e.599cf243000000000000000000000000.0 To: sip:121212_6666@192.168.99.112 From: <sip:121212_6666@192.168.99.112
;tag=7e4f6993bfbf831f6b016fea6683cdca-b98a
CSeq: 10 REGISTER Call-ID: 2bc5fd1061b31723-1350@192.168.99.111 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.1.6 (x86_64/linux)) Contact: <sip:121212_6666@192.168.99.111:5060> Expires: 0
The phone is then unregistered - the phone also shows "no service". It looks like Kamailio generates this message on it's own (and I don't know why).
I am still learning to implement kamailio as proxy. Reading the docs, I would expect Kamailio to automatically eval the correct parameter:
If the processed message contains neither Expires HFs nor expires contact parameters, this value will be used for newly created usrloc records.
[1]
What did I miss? Phones which use the Expire-header are working fine.
Kind regards Kevin
[1] default_expires - http://www.kamailio.org/docs/modules/5.2.x/modules/registrar.html
It's not clear what kamailio/asterisk integration method you are using. Looking at the 2 provided messages - the 2nd one is not a relay of the 1st one.
handle authentication/usrloc in Kamailio? or using PATH extension?
Cheers.
On Tue, Nov 6, 2018 at 4:00 PM Kevin Olbrich ko@sv01.de wrote:
Hi!
I have a phone (Mitel 6930) that does not send an Expire-header but "expire" in Contact during REGISTER:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:pbx.example.com SIP/2.0 Message Header Via: SIP/2.0/TLS 192.168.6.16:5061;branch=xxxxxxxxxxxxxxxx;rport Route: <sip:pbx.example.com;lr=lr;transport=tls> Max-Forwards: 70 From: "Example" <sip:121212_6666@pbx.example.com>;tag=b0cec92c3e To: "Example" <sip:121212_6666@pbx.example.com> Call-ID: aaaaaaaaaaaaaaaaa CSeq: 1190442896 REGISTER Accept-Language: de Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE,PRACK, SUBSCRIBE, INFO, PUBLISH Allow-Events: talk, hold, conference, LocalModeStatus Contact: "Example" <sip:121212_6666@192.0.2.1:62336
;+sip.instance="urn:uuid:00000000-0000-1000-8000-08000FB888F5";expires=300
Supported: path, gruu User-Agent: Mitel 6930/5.0.0.2041 Aastra-Line: 1 Aastra-Mac: AAAAAAAAAAAA Content-Length: 0This results in successful register, kamailio forwards REGISTER to asterisk (endpoint registered) and immediatly kamailio sends a new REGISTER with Expire set to 0 to asterisk:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:192.168.99.112:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.99.111:5060;branch=z9hG4bK9f9e.599cf243000000000000000000000000.0 To: sip:121212_6666@192.168.99.112 From: <sip:121212_6666@192.168.99.112
;tag=7e4f6993bfbf831f6b016fea6683cdca-b98a
CSeq: 10 REGISTER Call-ID: 2bc5fd1061b31723-1350@192.168.99.111 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.1.6 (x86_64/linux)) Contact: <sip:121212_6666@192.168.99.111:5060> Expires: 0The phone is then unregistered - the phone also shows "no service". It looks like Kamailio generates this message on it's own (and I don't know why).
I am still learning to implement kamailio as proxy. Reading the docs, I would expect Kamailio to automatically eval the correct parameter:
If the processed message contains neither Expires HFs nor expires contact parameters, this value will be used for newly created usrloc records.
[1]
What did I miss? Phones which use the Expire-header are working fine.
Kind regards Kevin
[1] default_expires - http://www.kamailio.org/docs/modules/5.2.x/modules/registrar.html _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga pojogas@gmail.com:
It's not clear what kamailio/asterisk integration method you are using. Looking at the 2 provided messages - the 2nd one is not a relay of the 1st one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk (this message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose level 3 has too much info.
Kevin
Cheers.
On Tue, Nov 6, 2018 at 4:00 PM Kevin Olbrich ko@sv01.de wrote:
Hi!
I have a phone (Mitel 6930) that does not send an Expire-header but "expire" in Contact during REGISTER:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:pbx.example.com SIP/2.0 Message Header Via: SIP/2.0/TLS 192.168.6.16:5061;branch=xxxxxxxxxxxxxxxx;rport Route: <sip:pbx.example.com;lr=lr;transport=tls> Max-Forwards: 70 From: "Example" <sip:121212_6666@pbx.example.com>;tag=b0cec92c3e To: "Example" <sip:121212_6666@pbx.example.com> Call-ID: aaaaaaaaaaaaaaaaa CSeq: 1190442896 REGISTER Accept-Language: de Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE,PRACK, SUBSCRIBE, INFO, PUBLISH Allow-Events: talk, hold, conference, LocalModeStatus Contact: "Example" <sip:121212_6666@192.0.2.1:62336
;+sip.instance="urn:uuid:00000000-0000-1000-8000-08000FB888F5";expires=300
Supported: path, gruu User-Agent: Mitel 6930/5.0.0.2041 Aastra-Line: 1 Aastra-Mac: AAAAAAAAAAAA Content-Length: 0This results in successful register, kamailio forwards REGISTER to asterisk (endpoint registered) and immediatly kamailio sends a new REGISTER with Expire set to 0 to asterisk:
Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:192.168.99.112:5060 SIP/2.0 Message Header Via: SIP/2.0/UDP 192.168.99.111:5060;branch=z9hG4bK9f9e.599cf243000000000000000000000000.0 To: sip:121212_6666@192.168.99.112 From: <sip:121212_6666@192.168.99.112
;tag=7e4f6993bfbf831f6b016fea6683cdca-b98a
CSeq: 10 REGISTER Call-ID: 2bc5fd1061b31723-1350@192.168.99.111 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.1.6 (x86_64/linux)) Contact: <sip:121212_6666@192.168.99.111:5060> Expires: 0The phone is then unregistered - the phone also shows "no service". It looks like Kamailio generates this message on it's own (and I don't know why).
I am still learning to implement kamailio as proxy. Reading the docs, I would expect Kamailio to automatically eval the correct parameter:
If the processed message contains neither Expires HFs nor expires contact parameters, this value will be used for newly created usrloc records.
[1]
What did I miss? Phones which use the Expire-header are working fine.
Kind regards Kevin
[1] default_expires - http://www.kamailio.org/docs/modules/5.2.x/modules/registrar.html _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga pojogas@gmail.com:
It's not clear what kamailio/asterisk integration method you are using. Looking at the 2 provided messages - the 2nd one is not a relay of the 1st one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk (this message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose level 3 has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
I would assume the phone sends multiple REGISTER requests with same CallID, one or more of which has an expire=0, as a NAT traversal technique trying to discover its public IP at first. May be it doesn't do it very well.
Since you are using Kamailio for auth/usrloc, sending its REGISTER with expire=0 would indicate that the Kamailio contact has expired (probably after such a request was received from the phone). Try checking it with 'kamctl ul show'
On Tue, Nov 6, 2018 at 4:57 PM Henning Westerholt hw@kamailio.org wrote:
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga <
pojogas@gmail.com>:
It's not clear what kamailio/asterisk integration method you are using. Looking at the 2 provided messages - the 2nd one is not a relay of the
1st
one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk (this message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose level 3 has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Am Di., 6. Nov. 2018 um 23:09 Uhr schrieb Sergiu Pojoga pojogas@gmail.com:
I would assume the phone sends multiple REGISTER requests with same CallID, one or more of which has an expire=0, as a NAT traversal technique trying to discover its public IP at first. May be it doesn't do it very well.
I have checked again and indeed, correct guess!
Since you are using Kamailio for auth/usrloc, sending its REGISTER with
expire=0 would indicate that the Kamailio contact has expired (probably after such a request was received from the phone). Try checking it with 'kamctl ul show'
Correct as well, endpoint is not listed there.
I will check if I can get debug from the phone.
Thank you very much!
Kevin
On Tue, Nov 6, 2018 at 4:57 PM Henning Westerholt hw@kamailio.org wrote:
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga <
pojogas@gmail.com>:
It's not clear what kamailio/asterisk integration method you are
using.
Looking at the 2 provided messages - the 2nd one is not a relay of
the 1st
one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk
(this
message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose level
3
has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hardly a guess, just experience, lol
You're welcome.
On Tue, Nov 6, 2018 at 5:24 PM Kevin Olbrich ko@sv01.de wrote:
Am Di., 6. Nov. 2018 um 23:09 Uhr schrieb Sergiu Pojoga <pojogas@gmail.com
:
I would assume the phone sends multiple REGISTER requests with same CallID, one or more of which has an expire=0, as a NAT traversal technique trying to discover its public IP at first. May be it doesn't do it very well.
I have checked again and indeed, correct guess!
Since you are using Kamailio for auth/usrloc, sending its REGISTER with
expire=0 would indicate that the Kamailio contact has expired (probably after such a request was received from the phone). Try checking it with 'kamctl ul show'
Correct as well, endpoint is not listed there.
I will check if I can get debug from the phone.
Thank you very much!
Kevin
On Tue, Nov 6, 2018 at 4:57 PM Henning Westerholt hw@kamailio.org wrote:
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga <
pojogas@gmail.com>:
It's not clear what kamailio/asterisk integration method you are
using.
Looking at the 2 provided messages - the 2nd one is not a relay of
the 1st
one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk
(this
message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose
level 3
has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi!
I have found the problem. It is indeed desired behaviour! Current FW is 5.1.0. I have now browsed the realease notes from latest to oldest and release 5.0.0 (first for Mitel 6900 series) states, that this phone only works, if registered to Mitel call servers. This remark is only listet there and in no other location. Seems like all who buy this phone are currently out of luck. The phone does not detect a Mitel call server and throws an internal 606 and disables the line until reboot. Source: Page 14 of Mitel 6800/6900 Series SIP Phones 5.0.0 Release Notes
I never had such a case, where a vendor locks his phone to it's own platform. In particular does not communicate this change.
Thanks for your help while debugging this. I have learned a lot during debug.
Kind regards Kevin
Am Di., 6. Nov. 2018 um 23:30 Uhr schrieb Sergiu Pojoga pojogas@gmail.com:
Hardly a guess, just experience, lol
You're welcome.
On Tue, Nov 6, 2018 at 5:24 PM Kevin Olbrich ko@sv01.de wrote:
Am Di., 6. Nov. 2018 um 23:09 Uhr schrieb Sergiu Pojoga < pojogas@gmail.com>:
I would assume the phone sends multiple REGISTER requests with same CallID, one or more of which has an expire=0, as a NAT traversal technique trying to discover its public IP at first. May be it doesn't do it very well.
I have checked again and indeed, correct guess!
Since you are using Kamailio for auth/usrloc, sending its REGISTER with
expire=0 would indicate that the Kamailio contact has expired (probably after such a request was received from the phone). Try checking it with 'kamctl ul show'
Correct as well, endpoint is not listed there.
I will check if I can get debug from the phone.
Thank you very much!
Kevin
On Tue, Nov 6, 2018 at 4:57 PM Henning Westerholt hw@kamailio.org wrote:
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga <
pojogas@gmail.com>:
It's not clear what kamailio/asterisk integration method you are
using.
Looking at the 2 provided messages - the 2nd one is not a relay of
the 1st
one.
I might have matched the wrong transaction. I use HEP/HOMER to observe communication and Kamailio starts a new flow (=Call-Id) to asterisk
(this
message is no coming from the phone).
handle authentication/usrloc in Kamailio? or using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose
level 3
has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
For anyone interested: server_header="Server: Mitel Border GW"
This effectively forges the header to the one from the firmware. There are many other: Aastra 800 OpenCom Aastra 400 MiVoice Office 400 Aastra MX-ONE Forum 5 Telepo Mitel-5000-ICP Mitel Border GW Mitel-3300-ICP
Source: - binwalk -e 6930.st - jffs2-root/fs_1/bin/linemgrSip will be of interest
security through obscurity
Kevin
Am Mi., 7. Nov. 2018 um 15:06 Uhr schrieb Kevin Olbrich ko@sv01.de:
Hi!
I have found the problem. It is indeed desired behaviour! Current FW is 5.1.0. I have now browsed the realease notes from latest to oldest and release 5.0.0 (first for Mitel 6900 series) states, that this phone only works, if registered to Mitel call servers. This remark is only listet there and in no other location. Seems like all who buy this phone are currently out of luck. The phone does not detect a Mitel call server and throws an internal 606 and disables the line until reboot. Source: Page 14 of Mitel 6800/6900 Series SIP Phones 5.0.0 Release Notes
I never had such a case, where a vendor locks his phone to it's own platform. In particular does not communicate this change.
Thanks for your help while debugging this. I have learned a lot during debug.
Kind regards Kevin
Am Di., 6. Nov. 2018 um 23:30 Uhr schrieb Sergiu Pojoga <pojogas@gmail.com
:
Hardly a guess, just experience, lol
You're welcome.
On Tue, Nov 6, 2018 at 5:24 PM Kevin Olbrich ko@sv01.de wrote:
Am Di., 6. Nov. 2018 um 23:09 Uhr schrieb Sergiu Pojoga < pojogas@gmail.com>:
I would assume the phone sends multiple REGISTER requests with same CallID, one or more of which has an expire=0, as a NAT traversal technique trying to discover its public IP at first. May be it doesn't do it very well.
I have checked again and indeed, correct guess!
Since you are using Kamailio for auth/usrloc, sending its REGISTER with
expire=0 would indicate that the Kamailio contact has expired (probably after such a request was received from the phone). Try checking it with 'kamctl ul show'
Correct as well, endpoint is not listed there.
I will check if I can get debug from the phone.
Thank you very much!
Kevin
On Tue, Nov 6, 2018 at 4:57 PM Henning Westerholt hw@kamailio.org wrote:
Am Dienstag, 6. November 2018, 22:50:54 CET schrieb Kevin Olbrich:
Am Di., 6. Nov. 2018 um 22:40 Uhr schrieb Sergiu Pojoga <
pojogas@gmail.com>:
> It's not clear what kamailio/asterisk integration method you are
using.
> Looking at the 2 provided messages - the 2nd one is not a relay of
the 1st
> one.
I might have matched the wrong transaction. I use HEP/HOMER to
observe
communication and Kamailio starts a new flow (=Call-Id) to asterisk
(this
message is no coming from the phone).
> handle authentication/usrloc in Kamailio? > or > using PATH extension?
I do auth + usrloc in Kamailio, no PATH.
Maybe the Kamailio debug would lead me to the problem but verbose
level 3
has too much info.
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Am Di., 6. Nov. 2018 um 22:57 Uhr schrieb Henning Westerholt < hw@kamailio.org>:
Hi Kevin,
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
Hi Henning,
even with an isolated setup (which this one currently is) I get several hundred lines per transaction. Comparing the debug of asterisk against kamailio, asterisk is much more readable for me. Maybe I need more training ;-)
Is there a starter guide to kamailio.cfg debug? It very much looks like a compiler log.
Kevin
Best regards,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services Kamailio security assessment - https://skalatan.de/de/assessment
Am Dienstag, 6. November 2018, 23:11:41 CET schrieb Kevin Olbrich:
you could control the time when the specific not-working phone send a REGISTER. Then you can enable the debugging for a few seconds during this time, and then deactivate it again. This should work even on a production server. Debugging it on a test server is of course an even better way.
even with an isolated setup (which this one currently is) I get several hundred lines per transaction. Comparing the debug of asterisk against kamailio, asterisk is much more readable for me. Maybe I need more training ;-)
Is there a starter guide to kamailio.cfg debug? It very much looks like a compiler log.
Hi Kevin,
I like this comparison, compiler log. ;-)
But you are right, it is really verbose in the debugging log level. I am not aware of a dedicated guide to this.
But you should be able with grep to filter the output of certain modules (look at the prefix).
Another idea is to enable the configuration debugger module, but this will help more if it is a cfg issue, and not a module issue. Have a look to the module README for more details about it capabilities.
Best regards,
Henning
-
Henning Westerholt -
Kevin Olbrich -
Sergiu Pojoga