how to make a sip call from outside sip server to FMG?

Question

i want to route some calls from an outside SIP server to a flash client(e.g. the sample flash phone) registered to an FMG, the SIP server can be configured to forward the SIP call request with predefined prefix e.g. "8***" to the FMG, but it seems that the FMG rejects them even i have re-configured the dialplan in workflow.xml as follows:

...

	<Condition variable="destNum" value="^8...$">
	<AppNode sequence="1" app="bridge" args="rtmp\|${destNum}@profile_default"/>
	<AppNode sequence="2" app="hangup" args="null"/>
	</Condition>

...

i added the above conditions to all contexts, "sipPhoneContext","sipGatewayContext","rtmp", but all dont work.

How to configure workflow.xml as well as other xmls to make it work? For other SIP server, it is a easy-to-implement feature to take call forwarding from other servers.

BTW, is there a detailed guidance on FMG configuration? I even dont know what other "variables" are besides "destNum"?

Thanks

Honggang

Anonymous · Answer

When a call is received by SIP Interface of FMG. Here is how it flows down (to FMS, if intended so). To troubleshoot, you would need to go through core.log files to find out at which point FMG is rejecting the call Leg coming from SIP server.

1) New Call arrives at FMG. How this call is authenticated is dependent upon configurations in sip.xml. A call should get authenticated(with a <profile> in sip ) so that it finds the call flow <context> it needs to execute. This call flow <context> will either be as specified in the <profile> to which FMG is able to assciate call leg (based upon sip IP/username etc). sip.xml also allows a default context to be used for any unidentified call which arrives at sip interface. Once FMG is able to locate a <context> string it tries to locate it in workflow.xml. FMG rejects a callLeg if it fails to identify a callLeg with a context in sip.xml or it doesn't find the full description of context string in workflow.xml.

2) Depending upon targetted workflow, FMG tried to find a suitable action to be taken on the callLeg, if no matching action is found, call is rejected.

3) If a action is found like "bridge" args="rtmp|${destNum}@profile_default"/>" ; FMG tries to see if it has a connection with "rtmp" application with profile_default. description of profile_default is listed in rtmp.xml. If a connection is found, call is forwarded to FMS application, else call is rejected with Not_found..

Once you could identify at which point call is failing, it would be easier to more forward with corrective configuration change.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded