Hi !
Struggling of moving a customer from ISDN to SIP, everything seems to work except for the Aut Att. The system responds to 404 not found.
a small number series is still on the ISDN for testing and this work. Any ideas , I have of course set the Automatic Attendant to YES and the same Calling party rights COS as the ISDN setting ...
Any ideas ....
Regards ...
/S
Aut. Att on 9.1 via SIP.
Re: Aut. Att on 9.1 via SIP.
AA should work on SIP.
Check traces properly with mototrace 3 or higher, and remember that DTMF is even more complicated on SIP, several ways to transfer digits (inband, outband), payload coding etc - all that should be identical to work.
Check traces properly with mototrace 3 or higher, and remember that DTMF is even more complicated on SIP, several ways to transfer digits (inband, outband), payload coding etc - all that should be identical to work.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: Aut. Att on 9.1 via SIP.
Thanks you very much for your concern and rapid answer,
The previous problem with barred DDI to SIP trunk call was in the local sip/proxy. only auth inc. call. disabled this and now I can make incoming DDI call thru the SIP trunk ....
But he Aut Att. issue I've tried with 11.2 and have the same same problem , so it must be a config. error some where... I see the Aut Att access number in the numbering plan so It is really there ...
The funny thing is that I have two 11.2 systems ...
*************** On the system where Aut Att is working:
Tue Mar 26 22:28:35 2024 ** SIP TRUNKING **
Tue Mar 26 22:28:35 2024 1162[sendLgEvtSipCreate] get pilot ok trunk : 4 <<<<<<< Is that the SIP trunk ? (see below)
Tue Mar 26 22:28:35 2024 [ipc_thread] Normal case : evt 10764
Tue Mar 26 22:28:35 2024 [ipc_thread] IPC Thread : Ipc reception 5661.
Tue Mar 26 22:28:35 2024 [ipc_thread] IPC Thread : TCL thread signaled.
Tue Mar 26 22:28:35 2024 [CMotorCallManager::insertCallwithEqt] CMotorCall 1262 inserted.
Tue Mar 26 22:28:35 2024 1162[sendLgEvtSipCreate] Event sent on eqt : 1262
************** On the system where Aut Att is NOT working:
Tue Mar 26 22:36:23 2024 ** SIP UNKNOWN ** <<<< Strange
Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] get pilot ok trunk : 10 <<<<<<< nr 10 in this system is the trunk for sipdevices !!!!
Tue Mar 26 22:36:23 2024 [ipc_thread] Normal case : evt 10767
Tue Mar 26 22:36:23 2024 [ipc_thread] IPC Thread : Ipc reception 13236.
Tue Mar 26 22:36:23 2024 [ipc_thread] IPC Thread : TCL thread signaled.
Tue Mar 26 22:36:23 2024 [CMotorCallManager::insertCallwithEqt] CMotorCall 2560 inserted.
Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] Event sent on eqt : 2560
After almost 50 hours on three days , my focus are becoming a little blur, I'm not in the twenties when I was a programmer ...
So if you have an hint on what can be wrong , please give me some advice ...
Regards ...
Stefan
The previous problem with barred DDI to SIP trunk call was in the local sip/proxy. only auth inc. call. disabled this and now I can make incoming DDI call thru the SIP trunk ....
But he Aut Att. issue I've tried with 11.2 and have the same same problem , so it must be a config. error some where... I see the Aut Att access number in the numbering plan so It is really there ...
The funny thing is that I have two 11.2 systems ...
*************** On the system where Aut Att is working:
Tue Mar 26 22:28:35 2024 ** SIP TRUNKING **
Tue Mar 26 22:28:35 2024 1162[sendLgEvtSipCreate] get pilot ok trunk : 4 <<<<<<< Is that the SIP trunk ? (see below)
Tue Mar 26 22:28:35 2024 [ipc_thread] Normal case : evt 10764
Tue Mar 26 22:28:35 2024 [ipc_thread] IPC Thread : Ipc reception 5661.
Tue Mar 26 22:28:35 2024 [ipc_thread] IPC Thread : TCL thread signaled.
Tue Mar 26 22:28:35 2024 [CMotorCallManager::insertCallwithEqt] CMotorCall 1262 inserted.
Tue Mar 26 22:28:35 2024 1162[sendLgEvtSipCreate] Event sent on eqt : 1262
************** On the system where Aut Att is NOT working:
Tue Mar 26 22:36:23 2024 ** SIP UNKNOWN ** <<<< Strange
Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] get pilot ok trunk : 10 <<<<<<< nr 10 in this system is the trunk for sipdevices !!!!
Tue Mar 26 22:36:23 2024 [ipc_thread] Normal case : evt 10767
Tue Mar 26 22:36:23 2024 [ipc_thread] IPC Thread : Ipc reception 13236.
Tue Mar 26 22:36:23 2024 [ipc_thread] IPC Thread : TCL thread signaled.
Tue Mar 26 22:36:23 2024 [CMotorCallManager::insertCallwithEqt] CMotorCall 2560 inserted.
Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] Event sent on eqt : 2560
After almost 50 hours on three days , my focus are becoming a little blur, I'm not in the twenties when I was a programmer ...
So if you have an hint on what can be wrong , please give me some advice ...
Regards ...
Stefan
Re: Aut. Att on 9.1 via SIP.
Without proper traces its not clear what could be wrong.
Do you have DID translation configured on SIP TG with AA?
Compare INVITES between normal DDI call and AA call line-by-line. Why "404 not found"?
Do you have DID translation configured on SIP TG with AA?
Compare INVITES between normal DDI call and AA call line-by-line. Why "404 not found"?
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: Aut. Att on 9.1 via SIP.
Again many thanks ...
*) Without proper traces its not clear what could be wrong. :: Do you mean a complete motortrace 9 / traced
*) Do you have DID translation configured on SIP TG with AA? :: Yes , the other numbers i same range could be called , except the Aut ATT
*) Compare INVITES between normal DDI call and AA call line-by-line. Why "404 not found"?
But I found the error, I hade to set the my SIP TG 10 (The systems sipdevices) with AA = Yes , so
the "Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] get pilot ok trunk : 10" shows that Automatic Att. wnats to use the "internal" SIP trunkgroup that is used for external SIP extensions is also handling AA calls ... despite the fact that the call request (invite) comes into the trunkgroup htat is connected into the external gw. ... probably I missed something in the docs ...
Anyway problem solved and many,many thanks for your valuable input.
Regards ...
Stefan
*) Without proper traces its not clear what could be wrong. :: Do you mean a complete motortrace 9 / traced
*) Do you have DID translation configured on SIP TG with AA? :: Yes , the other numbers i same range could be called , except the Aut ATT
*) Compare INVITES between normal DDI call and AA call line-by-line. Why "404 not found"?
But I found the error, I hade to set the my SIP TG 10 (The systems sipdevices) with AA = Yes , so
the "Tue Mar 26 22:36:23 2024 1103[sendLgEvtSipCreate] get pilot ok trunk : 10" shows that Automatic Att. wnats to use the "internal" SIP trunkgroup that is used for external SIP extensions is also handling AA calls ... despite the fact that the call request (invite) comes into the trunkgroup htat is connected into the external gw. ... probably I missed something in the docs ...
Anyway problem solved and many,many thanks for your valuable input.
Regards ...
Stefan
Re: Aut. Att on 9.1 via SIP.
we all knew that, we can't access INTERNALY AA without a loopback trkgp.
Re: Aut. Att on 9.1 via SIP.
Yes I know, but the call come from an external gateway via an SIP trunk directly connected to an outside carrier.. So in my opinion this trunksetup is of the same type as a ordinary E1/PRA trunk. What confused me if you look att my prev. post that the other 11.2 that system correctly selects trk 4 which is the external trunk, and the failed system selects rhe trk 10 which is the internal trunk.
For that behaviour I dont have any explanation nor solution...
For that behaviour I dont have any explanation nor solution...
