|
netsteller Posts: 29
3/10/2017
|
We upgraded from 1.0.0.44 to the new 1.0.3 and our outbound CID is doing some weird things. If I call my cell phone (T-Mobile) I get the wrong CID. If I call another cell phone (Sprint) the CID is unavailable. If I call my VoIP tech support the CID is wrong and even different from the wrong CID when calling my cell. Calling 3 different locations and the CID is different each time and always wrong. The PBX is setup with the correct CID and it was working before the upgrade.
Is there something in this new version that we need to change to update the outbound CID? Inbound is still working as expected.
|
|
|
0
link
|
|
bloxsupport1 Posts: 232
3/13/2017
|
what is the output of following command
$ rpm -qa | grep blox
|
|
|
0
link
|
|
bloxsupport1 Posts: 232
3/13/2017
|
Yes, the recent changes on CID caused the issue
Fixed: you can find the changes here https://github.com/blox-org/blox-cfg/commits/master
Patch upgrade is available here for download (Blox & freeblox rpm)
https://drive.google.com/open?id=0B5hujoHXcrfGbUhwY3RRMUF3aWs
verify and let us know
|
|
|
0
link
|
|
netsteller Posts: 29
3/22/2017
|
Ok, we finally got time to get this update installed. The first outbound call showed a "private" caller id. The second call and every call after that is still showing the wrong number just as before. No change.
|
|
|
0
link
|
|
netsteller Posts: 29
3/29/2017
|
We applied the fix and now the caller ID shows "unknown" when we call out. Is there a way to fix this so the PBX can get the callerID out correctly?
thx josh
edited by netsteller on 3/29/2017
|
|
|
0
link
|
|
bloxsupport1 Posts: 232
3/29/2017
|
It has been fixed and new release available for download 1.0.4-8 http://www.blox.org/downloads
|
|
|
0
link
|
|
netsteller Posts: 29
3/30/2017
|
The outbound callerID is still not working correctly. We have uploaded the new update 1.0.4.00-8. Called 2 different cell phones with 2 different carriers and the callerID is "private number". Called our VoIP carrier support and they got a "213" area code number. Not sure where this number even came from as we are in the "909" area code. They said something about checking the "remote party id" on our SBC if that makes sense.
edited by netsteller on 3/30/2017
edited by netsteller on 3/30/2017
|
|
|
0
link
|
|
bloxsupport1 Posts: 232
3/30/2017
|
Can you please send us the packet packet catpure on blox configured Internal and External SIP Profile ports, config backup and /var/log/opensips.log to [email protected]
1. use the following command to do packet capture
$ tcpdump -i any port internal-sip-port or port external-sip-port -w capture-file.pcap
upload the capture file and logs and share the link via email
2. config backup
Freeblox GUI -> Tools -> Config backup
3. output of following command
$ rpm -qa | grep blox
edited by bloxsupport1 on 3/30/2017
edited by bloxsupport1 on 3/30/2017
edited by bloxsupport1 on 3/30/2017
|
|
|
0
link
|
|
netsteller Posts: 29
4/4/2017
|
Just emailed it all to support.
thx josh
|
|
|
0
link
|
|
bloxsupport1 Posts: 232
4/6/2017
|
Got it. Trunk username should be left empty, if you are using IP Auth
|
|
|
0
link
|
|
netsteller Posts: 29
4/7/2017
|
That worked perfect. I think we had originally added the username for the trunk because it was required or something. But all is working now that we removed it.
thx josh
|
|
|
0
link
|