|
|
sup
Grünschnabel
Registration Date: 18.02.2006
Posts: 165
 |
|
I have reached an point of extreme frustration with this topic, and I think I am on to the root of the problem.
Problem: I authorize PBXes directly via IP address to an external SIP Proxy, and PBXes Passes Caller ID correctly to the outbound call. However as PBXes will not perform the complex LCR I need, then I have tried both sending calls to an Asterisk (for LCR) then the appropriate SIP proxies (after Asterisk LCR) , and now I have also tried the same with a VOIPSwitch. The VOIPSwitch is currently passing caller ID on Wholesale traffic as well as devices registered to it. One SIP proxy shows the caller ID passed to it. A Sample CDR is below.
supernettel-500 15036677700 UNITED STATES Oregon Apr 8, 2007 01:12:27 AM 00:00:00 00:00:00 0.000000
In the above example it is clearly the PBX User ID that is being passed to the SIP Proxy. Normally in that first field, is the outbound caller ID.
Suspected Source of Problem. There are two fields that can be potentially used for Caller ID. VoIPSwitch makes this clear in their documentation. I believe one field is called User ID . I suspect this USer ID is what is being looked at in both the case of Asterisk (by default in the version I have used) and the VoIPswitch.
Solution:
Set USER ID field to Caller ID number, as it seems it should be anyhow. This may or may not work with caller ID name as well. This will create a greater compatibility with all SIP Proxies, and prevent users from passing invalid caller ID to Providers that may reject calls based on valid ANI (which some do). I see no valid reason to pass the PBXes "USER-EXT" to an outbound trunk, but maybe I am missing the rationale behind it.
This post has been edited 3 time(s), it was last edited by sup on 08.04.2007 at 08:33.
|
|
08.04.2007 08:24 |
|
|
|
|
|
|
|