Asterisk 18.4.0
Configuration Manager 11.2.1.32
kamailio 5.4.4
Centos 7 build
Please help me understand the impact of this change/modification.
/etc/kamailio/include/main.cfg
line 925
I have an older vanilla asterisk that is taking PRI channels and converting to SIP and passing it to the DID's respective Asterisk Server.
Our old thirdlane responds to the UPDATE method with a '481 Call/Transaction Does Not Exist' and the Vanilla box acks it and keeps moving forward.
With the new TL MTE server, it sends back a 404 NOT FOUND error and the Vanilla box in response sends a CANCEL back and I hear busy tones.
When I switch the kamailio code in the above reference from a 404 to 481, I get my normal WARNING on vanilla that it cant match request UPDATE and the call continues to process like it does with the old TL MTE server.
Also, in reviewing the main.cfg from the v10 server running kamailio 5.3.3, it is not present.
Can someone let me know if this change is OK to keep in production or if this presents another unforeseen issue.
Thanks,
--E
Hello!
Please start Kamailio in debug mode. You will need to replace "#!define LOG_LEVEL L_ERR" with "#!define LOG_LEVEL L_DBG" in the /etc/kamailio/local.cfg configuration file and restart Kamailio. Then start SIP packet capture and repeat the call.
Please send packet capture and /var/log/kamailio.log file to volodya@thirdlane.com so I could check what happened there.
Thank you!