>>> On 3/14/2011 at 12:29 PM, in message <[email protected]>, Michael Scheidell <[email protected]> wrote: > On 3/14/11 12:19 PM, Michael Scheidell wrote: >> >> >> Best I can tell, sipx and the ITSP ignore the osi layer 7 (application >> layer) stuff.. don't know why, but it seems to work. inbound, >> outbound, two way audio, call transfers, caller id, hold, everything. > ok, with one exception. MOH. I get no MOH if the recipient puts me on > hold. might be layer 7 stuff. > dialing into an AA, then dialing an extension. > > if I dial into AA from a 'normal' ITSP, and dial an extension number, I > here the MOH when the call transfers, and the recipient puts me on hold, > and I hear MOH. > > if I dial into AA from a 'phucklated' ITSP (static ip, mucklated port > 5060 -> 5080), I don't here MOH when call transfers, and no MOH when > recipient puts me on hold. > > so, for anyone wanting to try this, yes, layer7 is important.
If your just not hearing MoH but the resume of the hold woks I'd look at a sip trace. MoH is really not much different than a transfer in the sipx world. The call is reinvited to the MoH server. Adn then when you resume the call is re transferred. So, I wouldn't' jump to "layer 7" issues so quickly. MoH works fine for the itsp we have used with port forwarding. And if the ITSP is not gonna work with port forwarding your only issue will not be listening MoH. Check if you doing MoH at the sipxbridge. If your not using Polycom then your Moh is done at sipxbridge and functions differently then using the default polycom method. -M _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
