- Joined
- Jul 2, 2021
- Messages
- 3
- Reaction score
- 0
Hello,
Can anyone help me with the following?
I'm receiving from the provider the Invite and 3CX immediately disconnects with 400 Bad Request
My interpretation is that the provider is not sending the From in the correct format. (missing SIP to address: +351923456765)
Is there any way to overcome this issue on the 3CX side?
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:[email protected]:5060;rinstance=49dba5575040e680 SIP/2.0
Message Header
Via: SIP/2.0/UDP z.z.z.z:5070;branch=z9hG4bKcljq73200gt4kbjssp60.1
To: <tel:+351yyyyyyyyy>
SIP to address: tel:+351yyyyyyyyy
From: tel:923456765;tag=p65540t1625163432m227516c26184s1_3642008593-846846844
SIP from tag: p65540t1625163432m227516c26184s1_3642008593-846846844
Call-ID: p65540t1625163432m227516c26184s2
[Generated Call-ID: p65540t1625163432m227516c26184s2]
CSeq: 1 INVITE
Max-Forwards: 65
Content-Length: 317
Contact: <sip:[email protected]:5070;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact URI: sip:[email protected]:5070;transport=udp
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Content-Type: application/sdp
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE
Accept: application/sdp
Supported: timer, 100rel, histinfo
Min-SE: 900
Session-Expires: 1800
P-Called-Party-ID: <tel:+351yyyyyyyyy>
P-Early-Media: supported
Session-ID: 1fe6ebf5255d313ddd7c9d7d37869196
P-Charging-Vector: icid-value=36kq5046p1ds2rk6ehcs2pg6hhoamfde9rpulo462jucmh78;icid-generated-at=z.z.z.z
Message Body
Can anyone help me with the following?
I'm receiving from the provider the Invite and 3CX immediately disconnects with 400 Bad Request
My interpretation is that the provider is not sending the From in the correct format. (missing SIP to address: +351923456765)
Is there any way to overcome this issue on the 3CX side?
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:[email protected]:5060;rinstance=49dba5575040e680 SIP/2.0
Message Header
Via: SIP/2.0/UDP z.z.z.z:5070;branch=z9hG4bKcljq73200gt4kbjssp60.1
To: <tel:+351yyyyyyyyy>
SIP to address: tel:+351yyyyyyyyy
From: tel:923456765;tag=p65540t1625163432m227516c26184s1_3642008593-846846844
SIP from tag: p65540t1625163432m227516c26184s1_3642008593-846846844
Call-ID: p65540t1625163432m227516c26184s2
[Generated Call-ID: p65540t1625163432m227516c26184s2]
CSeq: 1 INVITE
Max-Forwards: 65
Content-Length: 317
Contact: <sip:[email protected]:5070;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Contact URI: sip:[email protected]:5070;transport=udp
Contact parameter: +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"\r\n
Content-Type: application/sdp
Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PRACK, UPDATE, INVITE, ACK, OPTIONS, CANCEL, BYE
Accept: application/sdp
Supported: timer, 100rel, histinfo
Min-SE: 900
Session-Expires: 1800
P-Called-Party-ID: <tel:+351yyyyyyyyy>
P-Early-Media: supported
Session-ID: 1fe6ebf5255d313ddd7c9d7d37869196
P-Charging-Vector: icid-value=36kq5046p1ds2rk6ehcs2pg6hhoamfde9rpulo462jucmh78;icid-generated-at=z.z.z.z
Message Body