Cloud PBX to On-premises PSTN via SfB CCE

%3CLINGO-SUB%20id%3D%22lingo-sub-46618%22%20slang%3D%22en-US%22%3ECloud%20PBX%20to%20On-premises%20PSTN%20via%20SfB%20CCE%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46618%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20know%20if%20this%20is%20the%20right%20venue%20for%20this%20type%20of%20request%2Fpost.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20in%20the%20process%20of%20deploying%20SfB%20CCE%20to%20allow%20Cloud%20PBX%20users%20to%20utilize%20our%20existing%20PSTN%20connectivity.%20I%20have%20been%20sucessful%20in%20routing%20a%20call%20from%20my%20PSTN%20gateway%20thru%20CCE%20to%20SfB%20Online%2C%20however%2C%20I%20can%20not%20compete%20a%20call%20in%20the%20opposite%20direction.%20I%20have%20reviewed%20logs%20on%20the%20CCE%20Appliance%20and%20the%20gateway%20and%2C%20with%20my%20limitied%20knowedge%2C%20believe%20the%20issue%20is%20in%20the%20TO%20header.%20The%20TO%20header%20appears%20to%20be%20missing%20the%20target%20number.%20I%20am%20concerned%20however%20that%20this%20is%20by%20design%20and%20I%20have%20just%20never%20encountered%20it%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20the%20headers%20for%20the%20test%20call%3A%3C%2FP%3E%3CP%3EFrom%3A%20%26lt%3B5068%26gt%3B%3Bepid%3D3CBB68D14B%3Btag%3D6b3b3fa822%3CBR%20%2F%3ETo%3A%20%26lt%3B10.4.50.10%26gt%3B%3Btag%3D1BD2820-1499%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20have%20expected%20to%20see%20somthing%20like%26lt%3B1234567%26gt%3B.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThoughts%3F%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-46618%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20PBX%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46797%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20PBX%20to%20On-premises%20PSTN%20via%20SfB%20CCE%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46797%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EMohammed%2C%20your%20understanding%20is%20correct%2C%20and%20thank%20you%20for%20taking%20the%20time.%20The%20situation%20was%20my%20fault.%20A%20configuration%20error%20in%20my%20firewall%20was%20causing%20the%20issue.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EThanks%20for%20your%20response%2C%20it%20set%20me%20on%20the%20right%20path.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46674%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20PBX%20to%20On-premises%20PSTN%20via%20SfB%20CCE%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46674%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michael%2C%3C%2FP%3E%0A%3CP%3EIf%20I%20understand%20this%20correct%2C%20You%20are%20having%20Problems%20with%20Outbound%20Dialing%20with%20CCE%2C%20Meaning%20SFB%20online%20User%20makes%20an%20outbound%20call%20to%20PSTN.%20In%20This%20case%20the%20Signalling%20would%20ideally%20work%20this%20way%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnline%20User%20CLient%20Sends%20Invite%20with%20a%20To%20header%20which%20will%20have%20the%20Telephone%20number%20called%20in%20the%20format%20%3CSTRONG%3ETo%3C%2FSTRONG%3E%3A%20%26lt%3B%26gt%3B%2C%20This%20Invite%20goes%20from%20CLient%20to%20Online%20FE%2FDirector%20--%26gt%3B%20Online%20Edge%20--%26gt%3B%20CCE%20Edge%20--%26gt%3B%20CCE%20mediation%20--%26gt%3B%26nbsp%3BPSTN%20gateway%3C%2FP%3E%0A%3CP%3ESo%20the%20To%20Header%20that%20you%20are%20seeing%20should%20ideally%20be%20the%20same%20throughout%2C%20What%20logs%20did%20you%20find%20the%20To%20header%20in%20the%20IP%20format%3F%20might%20be%20good%20to%20check%20the%20client%20log%20as%20well%20for%20the%20Outbound%20Invite%20to%20see%20what%20is%20the%20TO%20header%20there%20and%20then%20the%20incoming%20Invite%20into%20the%20CCE%20edge%20to%20see%20what%20is%20the%20To%20header%20in%20that%2C%20which%20should%20then%20be%20carried%20over%20to%20mediation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I don't know if this is the right venue for this type of request/post.

 

I am in the process of deploying SfB CCE to allow Cloud PBX users to utilize our existing PSTN connectivity. I have been sucessful in routing a call from my PSTN gateway thru CCE to SfB Online, however, I can not compete a call in the opposite direction. I have reviewed logs on the CCE Appliance and the gateway and, with my limitied knowedge, believe the issue is in the TO header. The TO header appears to be missing the target number. I am concerned however that this is by design and I have just never encountered it before.

 

Here are the headers for the test call:

From: <sip:MediationServer.sfbhybrid.local:5068;transport=Tcp;ms-opaque=105637b0f2750d73>;epid=3CBB68D14B;tag=6b3b3fa822
To: <sip:10.4.50.10>;tag=1BD2820-1499

 

I would have expected to see somthing like<sip:1234567@10.4.50.10>.

 

Thoughts?

2 Replies

Hi Michael,

If I understand this correct, You are having Problems with Outbound Dialing with CCE, Meaning SFB online User makes an outbound call to PSTN. In This case the Signalling would ideally work this way

 

Online User CLient Sends Invite with a To header which will have the Telephone number called in the format To: <sip:+1XXXXXXXXXX@Domain.com;user=phone>, This Invite goes from CLient to Online FE/Director --> Online Edge --> CCE Edge --> CCE mediation --> PSTN gateway

So the To Header that you are seeing should ideally be the same throughout, What logs did you find the To header in the IP format? might be good to check the client log as well for the Outbound Invite to see what is the TO header there and then the incoming Invite into the CCE edge to see what is the To header in that, which should then be carried over to mediation.

 

 

Mohammed, your understanding is correct, and thank you for taking the time. The situation was my fault. A configuration error in my firewall was causing the issue. Thanks for your response, it set me on the right path.