Latest script released by our team to help you manage the Protocol error in your OXE Incident Log
https://github.com/fgadot/AlcatelUnleas ... ol%20error

SIP trunk DID problem

Post Reply
d_ivanov
Member
Posts: 3
Joined: 27 Jun 2022 07:01

SIP trunk DID problem

Post by d_ivanov »

I have a very strange problem with OmniPCX Enterprise R12.3.1 m4.501.10.d. It is detected when I unsuccessfully try to make a call on a missed call on a sip phone 8008. and this problem is due to an incorrectly formed FROM field.
From: "892818009" <sip:10.18.0.20;user=phone>
As I understand it should be:
From: "892818009" <sip:892818009@10.18.0.20;user=phone>
Can someone help me fix the situation? :shock:
Q931 Signal variant ISDN-all

I'll give you a trace below:

23:51:03.096381 IP (tos 0xa0, ttl 59, id 25455, offset 0, flags [none], proto UDP (17), length 862)
sip.bisv.kz.5060 > cs3.5060: SIP, length: 834
INVITE sip:5551356@158.58.132.67 SIP/2.0
Via: SIP/2.0/UDP 93.190.23.2:5060;branch=z9hG4bK2d01706d;rport
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
To: <sip:5551356@158.58.132.67>
Contact: <sip:892818009@93.190.23.2>
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Fri, 23 Aug 2024 20:51:03 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Type: application/sdp
Content-Length: 284

v=0
o=root 4909 4909 IN IP4 93.190.23.2
s=session
c=IN IP4 93.190.23.2
t=0 0
m=audio 10510 RTP/AVP 8 0 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

23:51:03.097252 IP (tos 0xb8, ttl 64, id 25018, offset 0, flags [none], proto UDP (17), length 339)
cs3.5060 > sip.bisv.kz.5060: SIP, length: 311
SIP/2.0 100 Trying
To: <sip:5551356@158.58.132.67>
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 INVITE
Via: SIP/2.0/UDP 93.190.23.2:5060;received=93.190.23.2;branch=z9hG4bK2d01706d;rport=5060
Content-Length: 0


23:51:03.101572 IP (tos 0xb8, ttl 64, id 55159, offset 0, flags [none], proto UDP (17), length 922)
cs3.5060 > 10.18.2.138.5060: SIP, length: 894
INVITE sip:210@10.18.2.138:5060;transport=udp SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO
Supported: replaces,timer,path
User-Agent: OmniPCX Enterprise R12.3.1 m4.501.10.d
Session-Expires: 1800;refresher=uac
Min-SE: 900
Content-Type: application/sdp
To: "IT Office" <sip:210@10.18.0.20;user=phone>
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
Contact: <sip:10.18.0.20;transport=UDP>
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
CSeq: 51108496 INVITE
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
Max-Forwards: 70
Content-Length: 215

v=0
o=OXE 1724446263 1724446263 IN IP4 10.18.0.20
s=abs
c=IN IP4 93.190.23.2
t=0 0
m=audio 10510 RTP/AVP 8 101
a=sendrecv
a=rtpmap:8 PCMA/8000
a=ptime:20
a=maxptime:30
a=rtpmap:101 telephone-event/8000

23:51:03.102138 IP (tos 0xb8, ttl 64, id 25019, offset 0, flags [none], proto UDP (17), length 530)
cs3.5060 > sip.bisv.kz.5060: SIP, length: 502
SIP/2.0 180 Ringing
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE
Contact: sip:10.18.0.20
User-Agent: OmniPCX Enterprise R12.3.1 m4.501.10.d
To: <sip:5551356@158.58.132.67>;tag=e55b8c1ef8740f76a497a2c8694860b1
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 INVITE
Via: SIP/2.0/UDP 93.190.23.2:5060;received=93.190.23.2;branch=z9hG4bK2d01706d;rport=5060
Content-Length: 0


23:51:03.170103 IP (tos 0xa0, ttl 64, id 62666, offset 0, flags [none], proto UDP (17), length 631)
10.18.2.138.5060 > cs3.5060: SIP, length: 603
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
To: "IT Office" <sip:210@10.18.0.20;user=phone>;tag=3541322697
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
CSeq: 51108496 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE
Contact: <sip:210@10.18.2.138:5060;transport=udp>;expires=300
Server: Alcatel-Lucent ICTouch-Phone 8008
Supported: answermode, eventlist, replaces, sdp-anat, timer
Content-Length: 0




23:51:08.966578 IP (tos 0xa0, ttl 59, id 25456, offset 0, flags [none], proto UDP (17), length 377)
sip.bisv.kz.5060 > cs3.5060: SIP, length: 349
CANCEL sip:5551356@158.58.132.67 SIP/2.0
Via: SIP/2.0/UDP 93.190.23.2:5060;branch=z9hG4bK2d01706d;rport
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
To: <sip:5551356@158.58.132.67>
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 CANCEL
User-Agent: Asterisk PBX
Max-Forwards: 70
Content-Length: 0


23:51:08.968772 IP (tos 0xb8, ttl 64, id 25020, offset 0, flags [none], proto UDP (17), length 417)
cs3.5060 > sip.bisv.kz.5060: SIP, length: 389
SIP/2.0 200 OK
Supported: timer,path,100rel
User-Agent: OmniPCX Enterprise R12.3.1 m4.501.10.d
To: <sip:5551356@158.58.132.67>
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 CANCEL
Via: SIP/2.0/UDP 93.190.23.2:5060;received=93.190.23.2;branch=z9hG4bK2d01706d;rport=5060
Content-Length: 0


23:51:08.969410 IP (tos 0xb8, ttl 64, id 55160, offset 0, flags [none], proto UDP (17), length 501)
cs3.5060 > 10.18.2.138.5060: SIP, length: 473
CANCEL sip:210@10.18.2.138:5060;transport=udp SIP/2.0
Supported: replaces,timer,path,100rel
User-Agent: OmniPCX Enterprise R12.3.1 m4.501.10.d
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
To: "IT Office" <sip:210@10.18.0.20;user=phone>
CSeq: 51108496 CANCEL
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
Max-Forwards: 70
Content-Length: 0


23:51:08.969755 IP (tos 0xb8, ttl 64, id 25021, offset 0, flags [none], proto UDP (17), length 516)
cs3.5060 > sip.bisv.kz.5060: SIP, length: 488
SIP/2.0 487 Request Terminated
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE
User-Agent: OmniPCX Enterprise R12.3.1 m4.501.10.d
To: <sip:5551356@158.58.132.67>;tag=e55b8c1ef8740f76a497a2c8694860b1
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 INVITE
Via: SIP/2.0/UDP 93.190.23.2:5060;received=93.190.23.2;branch=z9hG4bK2d01706d;rport=5060
Content-Length: 0


23:51:08.971604 IP (tos 0xa0, ttl 59, id 25457, offset 0, flags [none], proto UDP (17), length 450)
sip.bisv.kz.5060 > cs3.5060: SIP, length: 422
ACK sip:5551356@158.58.132.67 SIP/2.0
Via: SIP/2.0/UDP 93.190.23.2:5060;branch=z9hG4bK2d01706d;rport
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
To: <sip:5551356@158.58.132.67>;tag=e55b8c1ef8740f76a497a2c8694860b1
Contact: <sip:892818009@93.190.23.2>
Call-ID: 02796a0768b119206bab62f31b618f67@93.190.23.2
CSeq: 102 ACK
User-Agent: Asterisk PBX
Max-Forwards: 70
Content-Length: 0


23:51:08.978916 IP (tos 0xa0, ttl 64, id 62667, offset 0, flags [none], proto UDP (17), length 411)
10.18.2.138.52753 > cs3.5060: SIP, length: 383
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
To: "IT Office" <sip:210@10.18.0.20;user=phone>;tag=3541322697
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
CSeq: 51108496 CANCEL
Server: Alcatel-Lucent ICTouch-Phone 8008
Content-Length: 0


23:51:08.979842 IP (tos 0xa0, ttl 64, id 62668, offset 0, flags [none], proto UDP (17), length 579)
10.18.2.138.5060 > cs3.5060: SIP, length: 551
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
To: "IT Office" <sip:210@10.18.0.20;user=phone>;tag=3541322697
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
CSeq: 51108496 INVITE
Allow: ACK, BYE, CANCEL, INFO, INVITE, MESSAGE, NOTIFY, OPTIONS, REFER, SUBSCRIBE, UPDATE
Server: Alcatel-Lucent ICTouch-Phone 8008
Supported: answermode, eventlist, replaces, sdp-anat, timer
Content-Length: 0


23:51:08.980459 IP (tos 0xb8, ttl 64, id 55161, offset 0, flags [none], proto UDP (17), length 419)
cs3.5060 > 10.18.2.138.5060: SIP, length: 391
ACK sip:210@10.18.2.138:5060;transport=udp SIP/2.0
Call-ID: 2206cae10371c93f439b29c7d87051ba@10.18.0.20
From: "892818009 " <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3
To: "IT Office" <sip:210@10.18.0.20;user=phone>;tag=3541322697
Via: SIP/2.0/UDP 10.18.0.20;branch=z9hG4bKf50468aea937f75416359adbc1cedcf6
CSeq: 51108496 ACK
Max-Forwards: 70
Content-Length: 0
User avatar
frank
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3271
Joined: 06 Jul 2004 00:18
Location: New York
Contact:

Re: SIP trunk DID problem

Post by frank »

can you break down the calls. same trace. use motor trace 2 for log level
seems like a domain not setup in your gateway maybe?
Code Free Or Die
d_ivanov
Member
Posts: 3
Joined: 27 Jun 2022 07:01

Re: SIP trunk DID problem

Post by d_ivanov »

The above trace is one call from number 892818009 to number 5551356, after the call goes through DID 5551356 is converted to 210, at the moment of conversion from 5551356 to 210 in the FROM field the URI changes:
From: "892818009" <sip:892818009@93.190.23.2>;tag=as3d9e65b6
to
From: "892818009" <sip:10.18.0.20;user=phone>;tag=54141df46e87c8258f92d4988c5025a3

in attachment traced 2
You do not have the required permissions to view the files attached to this post.
Last edited by d_ivanov on 26 Aug 2024 12:52, edited 1 time in total.
d_ivanov
Member
Posts: 3
Joined: 27 Jun 2022 07:01

Re: SIP trunk DID problem

Post by d_ivanov »

when calling a missed call on phone 210, the IP address is substituted
From: 10.18.2.138 <sip:10.18.2.138@10.18.0.20>;tag=964875b4c7
To: "10.18.0.20" <sip:10.18.0.20@10.18.0.20>
User avatar
frank
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3271
Joined: 06 Jul 2004 00:18
Location: New York
Contact:

Re: SIP trunk DID problem

Post by frank »

What's your NPD like on this trunk?
Code Free Or Die
d_ivanov
Member
Posts: 3
Joined: 27 Jun 2022 07:01

Re: SIP trunk DID problem

Post by d_ivanov »

I tried
Public NPD ID 3
Description identifier 3
Name U_U_E_E_DDI
Calling Numbering plan ident. Unknown
Called numbering plan ident. Unknown
Authorize personal calling num use False
Install. number source Entity source
Default number source Entity source
Called DID identifier 0
Calling/Connected DID identifier 0
and
Public NPD ID 10
Description identifier 10
Name IU_IU_E_E_DDI
Calling Numbering plan ident. NPI/TON: ISDN Unknown
Called numbering plan ident. NPI/TON: ISDN Unknown
Authorize personal calling num use False
Install. number source Entity source
Default number source Entity source
Called DID identifier 0
Calling/Connected DID identifier 0

Private NPD ID 0
Management Mode Automatic
Public DID transcoding - Tru
Last edited by d_ivanov on 27 Aug 2024 09:37, edited 1 time in total.
haroun
Senior Member
Posts: 1396
Joined: 29 Mar 2010 11:09

Re: SIP trunk DID problem

Post by haroun »

8008 in sip mode ?CHECK THE ACCOUNT setting
header issue
invite no conform
iNVITE
Mon Aug 26 19:41:31 2024 REQUEST URI : <> 5551356@158.58.132.67:5060 ; user=name
1724690491 -> Mon Aug 26 19:41:31 2024 FROM : <89281800> 89281800@93.190.23.2:5060 ; user=name
Mon Aug 26 19:41:31 2024 TO : <> 5551356@158.58.132.67:5060 ; user=name

89281800 is considerate as a name not a tel
invite in conformity
REQUEST URI : <> 077060@10.235.96.133:5060 ; user=phone
1724907286 -> FROM : <51009> 51009@10.235.96.130:5060 ; user=phone
1724907286 -> TO : <> 077060@10.235.96.133:5060 ; user=phone
-------------
even the contac fiel is wrong
o: "IT Office" <sip:210@10.18.0.20;user=phone>
From: "89281800" <sip:10.18.0.20;user=phone>;tag=503190a2a551065fdc03d4c013f70283
Contact: <sip:10.18.0.20;transport=UDP>
d_ivanov
Member
Posts: 3
Joined: 27 Jun 2022 07:01

Re: SIP trunk DID problem

Post by d_ivanov »

Good day haroun
8008 in sip mode
settings:
Directory Number
210

Directory name
IT

Directory First Name
Office

UTF-8 Directory Name
IT Office

UTF-8 Directory First Name

Location Node
1

Shelf Address
255

Board Address
255

Equipment Address
255

Set Type
SIP extension

Sub type
IPTouch 8008

Entity Number
1

Set Function
Default

Domain Identifier
0

Language ID
1

Secret Code
****

Multi-line station
YES

Can be Called/Dialed By Name
YES

Phone book Name (Dial by name)
IT

Phone book First Name
Office

Displayed Name
IT Office



do you think that the invite package from the provider contains user=name instead of user=phone?
haroun
Senior Member
Posts: 1396
Joined: 29 Mar 2010 11:09

Re: SIP trunk DID problem

Post by haroun »

hi😊
TEL URI

If the phone has an assigned PSTN telephone number, this field should be set to "User=Phone". Then a "User=Phone" parameter will be attached to the Request-Line and "TO" header in the SIP request to indicate the E.164 number. If set to "Enable", "Tel:" will be used instead of "SIP:" in the SIP request.
Some sip phones have the ability to gonfig the tel uri
TEL URI.jpg
You do not have the required permissions to view the files attached to this post.
haroun
Senior Member
Posts: 1396
Joined: 29 Mar 2010 11:09

Re: SIP trunk DID problem

Post by haroun »

yep i just tried to make some changein a sip phone tel uri look what i got he was unable to call

RECEIVE MESSAGE FROM NETWORK (10.235.96.136:5060 [UDP])
----------------------utf8-----------------------
INVITE tel:51009 SIP/2.0
Via: SIP/2.0/UDP 10.235.96.136:5060;branch=z9hG4bK95831665;rport
Route: <sip:10.235.96.130:5060;lr>
From: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>;tag=1809968060
To: <tel:51009>
Call-ID: 525599149-5060-60@BA.CDF.JG.BDG
CSeq: 590 INVITE
Contact: "Salles Pompes lrb" <sip:553720@10.235.96.136:5060;user=phone>
Max-Forwards: 70
User-Agent: Grandstream GXP1615 1.0.4.55
P-Preferred-Identity: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>
P-Access-Network-Info: IEEE-EUI-48;eui-48-addr=AC-A0-16-AD-CA-75
P-Emergency-Info: IEEE-EUI-48;eui-48-addr=00-0B-82-BF-FD-B0
Supported: replaces, path, timer
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Type: application/sdp
Accept: application/sdp, application/dtmf-relay
Content-Length: 382


1725193743 -> SEND MESSAGE TO NETWORK (10.235.96.136:5060 [UDP]) (BUFF LEN = 292)
----------------------utf8-----------------------
SIP/2.0 100 Trying
To: <tel:51009>
From: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>;tag=1809968060
Call-ID: 525599149-5060-60@BA.CDF.JG.BDG
CSeq: 590 INVITE
Via: SIP/2.0/UDP 10.235.96.136:5060;received=10.235.96.136;branch=z9hG4bK95831665;rport=5060
Content-Length: 0

--endMessage (10.235.96.136:5060)
1725193743 -> SEND MESSAGE TO NETWORK (10.235.96.136:5060 [UDP]) (BUFF LEN = 292)
----------------------utf8-----------------------
SIP/2.0 100 Trying
To: <tel:51009>
From: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>;tag=1809968060
Call-ID: 525599149-5060-60@BA.CDF.JG.BDG
CSeq: 590 INVITE
Via: SIP/2.0/UDP 10.235.96.136:5060;received=10.235.96.136;branch=z9hG4bK95831665;rport=5060
Content-Length: 0

-------------------------------------------------

----------------------utf8-----------------------
SIP/2.0 416 Unsupported URI Scheme
To: <tel:51009>
From: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>;tag=1809968060
Call-ID: 525599149-5060-60@BA.CDF.JG.BDG
CSeq: 590 INVITE
Via: SIP/2.0/UDP 10.235.96.136:5060;received=10.235.96.136;branch=z9hG4bK95831665;rport=5060
Content-Length: 0

-------------------------------------------------

----------------------utf8-----------------------
ACK tel:51009 SIP/2.0
Via: SIP/2.0/UDP 10.235.96.136:5060;branch=z9hG4bK95831665;rport
Route: <sip:10.235.96.130:5060;lr>
From: "Salles Pompes lrb" <sip:553720@10.235.96.130;user=phone>;tag=1809968060
To: <tel:51009>
Call-ID: 525599149-5060-60@BA.CDF.JG.BDG
CSeq: 590 ACK
Content-Length: 0

-------------------------------------------------
Post Reply

Return to “SIP”