Markus Oestreicher

The problem here is identifying the sender: I have a trunk OCS->pbxnsip In OCS there are different users. Each user has an extension with the same name on pbxnsip. "Assume that call comes from user" is set to a fixed extension, all calls are accounted to the same user. However, I need different Dial Plans per User so I need to identfy the sending user. Leaving "Assume that call comes from user" empty, pbxnsip can recognize "From: user-extension@mediation-server" as local extension and works properly (old problem solved, see above) When call forwarding comes into play, OCS sends a "From: external-number@mediation-server" header. The numbers are completly random... For these numbers there is no local extensions, therefore error "Could not identify user" For this to work, I need a behaviour: if "From:" matches a known extension use this one, else "Assume that calls come from fixed extension xyz" Do you have any idea? Markus

I need to re-open this topic with a new issue: After implementing the two steps above, identifying the outgoing user works. The only downside is, call forwarding does not work. When the call is forwarded, pbxnsip receives the following request: INVITE sip:forwarding-destination@pbxnsip;user=phone SIP/2.0 FROM: <sip:original-caller-id@ocs.domain;user=phone>;epid=68F4D0A0C6;tag=885932eb2 TO: <sip:forwarding-destination@pbxnsip;user=phone> The problem lies in the From: field. It contains the original caller's number, so the user is not recognized locally: [5] 2009/02/13 19:30:36: Trunk call: Could not identify user Could you implement a feature like "Try to identify user, otherwise assume that call comes from user:" for this case? bye Markus

Hello Jan, I read that OCS R2 supported a new feature like "Direct SIP" http://msgoodies.blogspot.com/2008/09/dire...n-ocs-2007.html http://communicationsserverteam.com/archiv.../09/26/270.aspx Maybe we don't need the Mediation Server any more? Did you already have a look on that? bye Markus

I am having the same problem. [1] 2008/09/12 15:31:20: No TLS session key in Server Hello Done [5] 2008/09/12 15:31:20: SMTP: Connection refused on 192.168.192.6:25 It seems that TLS is tried automatically - we don't need it. How can we disable that? Markus

"Alias" was the right keyword. I have solved it using two things: 1. OCS uses E.164 format, so I added +900 as an Alias for extension 900 2. I have added the FQDN of the mediation server as an Alias for the SIP domain. This way an incoming OCS call with header "From: +900@<fqdn-of-ocs-med>" will be accounted to the local extension 900. Now I have different Dial Plans dependant on the OCS user calling. @pbxnsip: Can step 2 lead to unexpected problems I don't see currently? Thanks Markus

Can you give me some advice on this? Do you need more information about the setup?

We have set up the integration with OCS using the Wiki page. Basically everything works fine. I want to have different dial plans for different users for outgoing calls from OCS. While setting up you have to set "Assume that call comes from user" to one of your extensions. This way all outgoing calls from OCS will have this user as caller-id and will use the same dial plan. How should the trunk be configured that it can identify the extension on its own? The calls from OCS seem to come from +xxx@<fqdn-of-mediation-server>. I need to map xxx to a local extension. Thanks! Markus