- Joined
- Dec 19, 2018
- Messages
- 22
- Reaction score
- 4
Hello all,
Ive got some weird stuff going on with a 3cx installation, ill try to explain:
We've got a SBC on site from the sip provider.
It accepts calls form our pbx if the from filed is 10 digits long. then it know how to route the calls.
Example:
Message Header
From: "0123456789"<sip:[email protected]:5060>;tag=42477926
SIP from display info: "0123456789"
SIP from address: sip:[email protected]:5060
SIP from tag: 42477926
But somehow in some cases the pbx changes the from field to the internal extension. (or it does not change it to the 10 digits)
Example:
Message Header
From: "19581"<sip:[email protected]:5060>;tag=42477926
SIP from display info: "19581"
SIP from address: sip:[email protected]:5060
SIP from tag: 42477926
Did anyone had this issue before?
It would make more sense if it was all the time or not.
We use yealink, snom and grandstream gxw4232. problem is on multiple devices.
Specs:
Windows Server 2016.
3CX v18.0 update 9 (Build 31)
Kind regards.
Ive got some weird stuff going on with a 3cx installation, ill try to explain:
We've got a SBC on site from the sip provider.
It accepts calls form our pbx if the from filed is 10 digits long. then it know how to route the calls.
Example:
Message Header
From: "0123456789"<sip:[email protected]:5060>;tag=42477926
SIP from display info: "0123456789"
SIP from address: sip:[email protected]:5060
SIP from tag: 42477926
But somehow in some cases the pbx changes the from field to the internal extension. (or it does not change it to the 10 digits)
Example:
Message Header
From: "19581"<sip:[email protected]:5060>;tag=42477926
SIP from display info: "19581"
SIP from address: sip:[email protected]:5060
SIP from tag: 42477926
Did anyone had this issue before?
It would make more sense if it was all the time or not.
We use yealink, snom and grandstream gxw4232. problem is on multiple devices.
Specs:
Windows Server 2016.
3CX v18.0 update 9 (Build 31)
Kind regards.