Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP issue...

Status
Not open for further replies.

wireman50

Technical User
Jan 8, 2011
1,023
GB
Weird one and its doing my head in (and provider) have got a call in to Mitel tech but thought I would ask here as well.

Have 2 SIP trunks setup on a 3300Cx MCD5.0 UR1.
Finally got everythinbg working as was unable to make off bnet calls to start with and an answer on here provided me with the clue to the answer.

BUT I have one issue that remains and is a bit of a show stopper. I can make calls to and from the proivider SIP network no problem. I can recieve calls from the PSTN no problem.

I can make a call to the PSTN and the call proceeds normally BUT I cannot hear the other party BUT they can hear me when they answer (i know they have answered because dial tone disappears and if they hang up the call clears on the 3300 (but not till they hang up))...on a 5312.

If I make the call on an analogue port on the 3300 we can hear each other no problem!

So it looks like an issue with the 3300 and/or the network (except of course that the analogue call is still going through the same network as the 5312...)

Anyone got any ideas before I have to buy a wig?

Just to be sure I have forwarded the ports (SIP and UDP for RTP)on the firewall and through NAT and have been told my router does not have SIP awareness or ALG on it....its just very strange that the problem is only on minet sets.

Any help gratefully recieved.
 
It's a network issue. You may have opened up the UDP ports that the MCD uses, but probably not those that the sets use.

Just thought of this, worth a try. Call one of your analogue sets from the 5312, then conference in the SIP call. This will force the media stream from the SIP trunk to go to the MCD (as it would when you call the ONS set from the SIP trunk). If you can now her the SIP trunk, that would prove the theory.
 
Turned out to be the router on the BB. Was rewriting the headers SIP_ALG stylee even though it (allegadly) di not have A:G on it. Changed the router to one where you could explicitly turn off ALG, did so, and it all worked hunky dory.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top