Incoming SIP call not routing to DDI

MartinB
Member
Posts: 92
Joined: 16 Mar 2011 03:30

Re: Incoming SIP call not routing to DDI

Post by MartinB »

Still doing the same Haroun. Not routing to DDI. :?

attached new Motortrace
Motortrace 3.txt
You do not have the required permissions to view the files attached to this post.
sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 692
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: Incoming SIP call not routing to DDI

Post by sadim »

Can you try adding the folowing ddi trancoding:
First external number :0027116893600
First Internal number :3600
sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 692
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: Incoming SIP call not routing to DDI

Post by sadim »

Case it does not work, try
First external number :116893600
First Internal number :3600
MartinB
Member
Posts: 92
Joined: 16 Mar 2011 03:30

Re: Incoming SIP call not routing to DDI

Post by MartinB »

Hi Sadim

Nope, I have tried all possibilities now.

┌─[ 4 ] Instances: Default DID num. translator─┐
│ │
│ -> 0027116893600 │
│ 0116893600 │
│ 116893600 │
│ 27116893600 │
│ │
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Incoming SIP call not routing to DDI

Post by haroun »

didtest command to see incoming ddi
also trace the call handelig with actbg ddi =on
10.1.102.31 IS OXE RIGHT?
see this
convertCSipURLIntoSipuri] bad TEL uri.
Mon Jun 26 15:03:10 2023 [getFromHeader3] =@10.1.102.31.
Mon Jun 26 15:03:10 2023 [getReqUriHeader] look at the requri.
Mon Jun 26 15:03:10 2023 [convertCSipURLIntoSipuri] uri = sip:+27116893674@172.31.16.7:5060;user=phone.
Mon Jun 26 15:03:10 2023 11ac[CMotorCall::getUserType] extGw=-1.
Mon Jun 26 15:03:10 2023 [CMotorCall::analyseRouting] TEL uri=1.
Mon Jun 26 15:03:10 2023 [CMotorCall::analyseRouting] @10.1.102.31 NOT found in the dictionnary.
Mon Jun 26 15:03:10 2023 [isDomainFromExtGw] Host from request is : 10.1.102.31.
Mon Jun 26 15:03:10 2023 [isDomainFromExtGw] User from request is :
Mon Jun 26 15:03:10 2023 Routing using Via Header
ALSO no direction in the sdp
MartinB
Member
Posts: 92
Joined: 16 Mar 2011 03:30

Re: Incoming SIP call not routing to DDI

Post by MartinB »

HI Haroun

yes 10.1.102.31 is the OXE

I will try create an extra SIP gateway with 172.31.16.7 as the remote domain just for the incoming?
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Incoming SIP call not routing to DDI

Post by haroun »

ok
but have a try with
tuner km
tuner ctr
trc i
actdbg npd=on
mtarcer -a

some of my output for incoming call through pcm an sip
get_right_NPDId_for_incoming_call octet3 0x7f TG 1800
(281914:000026) get_right_NPDId_for_incoming_call (default) public local_NPDId = 35
(281914:000027) get_Is_Incoming_Transcoded Result 1
(281914:000028) get_right_NPDId_for_incoming_call octet3 0x7f TG 1800
(281914:000029) get_right_NPDId_for_incoming_call (default) public local_NPDId = 35
(281914:000030) isdnmcdu_trace: 4888

sip(mobile)
rz_mess_t2 octet3_calling 1
(285421:000286) get_right_NPDId_for_incoming_call octet3 0x1 TG 1936
(285421:000287) get_right_NPDId_for_incoming_call localNPI_TON = 3, local_NPDId = 37
(285421:000288) ctrl_isdn_call_num_oct3X NPD_for_connected 37
(285421:000289) ctrl_isdn_call_num octet3=0x1 octet3a=0x81
(285421:000290) isdnmcdu_trace: 0770604647
(285421:000291) ctrl_isdn_call_num lg_n_org 10
(285421:000292) isdnmcdu_trace: 0770604647
(285421:000293) ctrl_isdn_call_num lg_mcdu_reseau 10
(285421:000294) ctrl_isdn_call_num CALLING lg_mcdu_reseau_2nd 0
(285421:000295) ctrl_isdn_call_num_oct3X stockage octet3_called
(285421:000296) ctrl_isdn_call_num_oct3X octet3_called 0x80
(285421:000297) ctrl_isdn_called: numcomp[1]=4
(285421:000298) ctrl_isdn_called: numcomp[2]=8
(285421:000299) ctrl_isdn_called: numcomp[3]=8
(285421:000300) ctrl_isdn_called: numcomp[4]=7
(285421:000301) get_right_NPDId_for_incoming_call octet3 0x0 TG 1936
(285421:000302) get_right_NPDId_for_incoming_call localNPI_TON = 0, local_NPDId = 37
(285421:000303) trad_did mode transparent bon_num=true
(285421:000304) get_right_NPDId_for_incoming_call octet3 0x0 TG 1936
(285421:000305) get_right_NPDId_for_incoming_call localNPI_TON = 0, local_NPDId = 37
(285421:000306) trad_did mode transparent bon_num=true
(285421:000307) get_right_NPDId_for_incoming_call octet3 0x0 TG 1936
(285421:000308) get_right_NPDId_for_incoming_call localNPI_TON = 0, local_NPDId = 37
(285421:000309) get_Is_Incoming_Transcoded Result 1
(285421:000310) get_right_NPDId_for_incoming_call octet3 0x0 TG 1936
(285421:000311) get_right_NPDId_for_incoming_call localNPI_TON = 0, local_NPDId = 37
(285421:000312) trad_did mode transparent bon_num=true
(285421:000313) isdnmcdu_trace: 4888
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Incoming SIP call not routing to DDI

Post by haroun »

sorry, the good syntax is
tuner km
tuner ctr
trc i
tuner +at +ico
actdbg npd=on
mtarcer -a
MartinB
Member
Posts: 92
Joined: 16 Mar 2011 03:30

Re: Incoming SIP call not routing to DDI

Post by MartinB »

attached is that trace Haroun.

It looks like it is picking up correct NPD and SIP GW and trunk according to the trace.

but still anonymous call routing

Its an ANONYMOUS Call --
(273545:000377:04055) anonymous_reroute Fin Result 1
(273545:000378:04055) DEST_APEL -- Its an Anonymous Call !! Reroute to entity...

tunker km.txt
You do not have the required permissions to view the files attached to this post.
sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 692
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: Incoming SIP call not routing to DDI

Post by sadim »

on the trunk, how is managed the parameter "Reroute Anonymous Calls to Entity"
Post Reply

Return to “SIP”