Alcatel Unleashed

Alcatel OXE V12.4 . Calls going to TMobile are being rejected I think because of 4 digit caller ID, but there isn't any issue with other carriers .


<--- Received SIP request (909 bytes) from UDP:10.50.160.44:5060 --->
INVITE sip:6129104073@147.187.132.21 SIP/2.0
Via: SIP/2.0/UDP 10.50.160.44:5060;rport;branch=z9hG4bKPj62026da8-d83f-4d38-84da-ac2e99953f49
From: "5505_SF_CS_JB" sip:5505@10.50.160.44;tag=43d003b0-e09f-41f0-92aa-d56d31c6ddf1
To: sip:6129104073@147.187.132.21
Contact: sip:asterisk@10.50.160.44:5060
Call-ID: 68b80638-d1d3-4d97-b42f-f657bf388f40
CSeq: 14048 INVITE
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Session-Expires: 1800
Min-SE: 90
Max-Forwards: 70
User-Agent: Spok 12.5.6
Content-Type: application/sdp
Content-Length: 240

v=0
o=- 2066981812 2066981812 IN IP4 10.50.160.44
s=Spok 12.5.6
c=IN IP4 10.50.160.44
t=0 0
m=audio 16394 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.50.160.44:5060;rport=5060;received=10.50.160.44;branch=z9hG4bKPj62026da8-d83f-4d38-84da-ac2e99953f49
Call-ID: 68b80638-d1d3-4d97-b42f-f657bf388f40
From: "5505_SF_CS_JB" sip:5505@10.50.160.44;tag=43d003b0-e09f-41f0-92aa-d56d31c6ddf1
To: sip:6129104073@147.187.132.21
CSeq: 14048 INVITE
Server: Spok 12.5.6
Content-Length: 0

SIP/2.0 486 Busy Here
Via: SIP/2.0/UDP 10.50.160.44:5060;rport=5060;received=10.50.160.44;branch=z9hG4bKPj62026da8-d83f-4d38-84da-ac2e99953f49
Call-ID: 68b80638-d1d3-4d97-b42f-f657bf388f40
From: "5505_SF_CS_JB" sip:5505@10.50.160.44;tag=43d003b0-e09f-41f0-92aa-d56d31c6ddf1
To: sip:6129104073@147.187.132.21;tag=4dae99ab-6e19-4763-a0ae-291af114f6e5
CSeq: 14048 INVITE
Server: Spok 12.5.6
Reason: Q.850;cause=17
Content-Length: 0


<--- Received SIP request (433 bytes) from UDP:10.50.160.44:5060 --->
ACK sip:6129104073@147.187.132.21 SIP/2.0
Via: SIP/2.0/UDP 10.50.160.44:5060;rport;branch=z9hG4bKPj62026da8-d83f-4d38-84da-ac2e99953f49
From: "5505_SF_CS_JB" sip:5505@10.50.160.44;tag=43d003b0-e09f-41f0-92aa-d56d31c6ddf1
To: sip:6129104073@147.187.132.21;tag=4dae99ab-6e19-4763-a0ae-291af114f6e5
Call-ID: 68b80638-d1d3-4d97-b42f-f657bf388f40
CSeq: 14048 ACK
Max-Forwards: 70
User-Agent: Spok 12.5.6
Content-Length: 0

can you have a caller id that pulses either 4 or 10 digits out?

hi
are there any changes made in the german numbring plan ? the called number area is 6129 should not target to a mobile network but to Schlangenbad Taunus .
the german mobilnet starts by 16 or 17, i think the carrier is expecting from you 0+16 xxxxxxxxxx or +4916xxxxxxxx

612 is the area code in Minnesota.

my bad
that was TMobile USA not Germany
the cause in the isdn Q931cause is 17,This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy it is noted that the user equipment is compatible with the call
Did u use DDI , did Tmobile accepts 4digits or is excepting 10 digits as caller party from ur side

I believe the issue is that t-mobile USA is expecting 10 digits, when all other providers are fine with 4 digits. I just don't know how to send 10 digits to t-mobile and 4 to all others.

Use a Different ARS route list and add digits, or create a new NPD with all the digits you need to sent to line, i had a similar issue when helping a site in LA,

aspire1245 wrote: ↑16 May 2022 11:15 I believe the issue is that t-mobile USA is expecting 10 digits, when all other providers are fine with 4 digits. I just don't know how to send 10 digits to t-mobile and 4 to all others.

1 - Build 10 digits Calling number (via NPD) and check t-mobile.
2 - If with t-mobile Ok - check with another calls (and 10 digits Calling number).

Ig 1 Ok but 2 NOK - you need to use ARS (as written before).