Alcatel Unleashed

My Pabx to cucm communities ok.. E1 call cannot reroute to sip trunk.. We raised a ticket on alcatel. Hopefully they're answer me

ahqswitchroom4466 wrote: ↑01 Sep 2024 15:10 My Pabx to cucm communities ok.. E1 call cannot reroute to sip trunk.. We raised a ticket on alcatel. Hopefully they're answer me

ok but i bet the issue is on CUCM side

After alcatel support i can told you where is the problem

ok
but let try something , play with those prameters in cucm for sip trunk to oxe 1XXrel or mtp

From my poin of view - problem in Alcatel management.
PBX receive Called number 9459010017
TG without DID transcoding - called number used without modification.
945 - ARS prefix. So we have just 7 digits 9010017.
But in discriminator 5 for Call number 9 written - number of digits 10.

@vad that's true what u said, user with that config has only to dial 7 digits starting by 9 and oxe add the 945 as per ars route list 5 but in reality user dial ars +digit 9+ 6 other digits
despite this we see in the invite toward the cucm the whole good number (10digits)
To: <sip:9459010017@10.100.20.30:5060;user=phone>
if it was an invalid number cucm should return 404 not found or 401
i think it's mismatche on maping sip to isdn error code mapping but but I insist on the fact that the problem comes from the CUCM

call flow for cisco as transit node between oxe and pstn; the called number doesn't exist but the 183 and prack are there
@10.235.96.133 is lan side for cisco &@172.22.54.28 is wan side
at the end the second route is proceedec as session traget is a server group

ahqswitchroom4466 wrote: ↑03 Sep 2024 05:40 After alcatel support i can told you where is the problem

hi any update

ahqswitchroom4466 wrote: ↑03 Sep 2024 05:40 After alcatel support i can told you where is the problem

no answer yet from ALU ?

haroun wrote: ↑01 Oct 2024 11:59

ahqswitchroom4466 wrote: ↑03 Sep 2024 05:40 After alcatel support i can told you where is the problem

no answer yet from ALU ?

Yes sir.. No answer yet from ALE support..