On 1/27/2011 12:27 PM, Matt White wrote:
>>> "Matthew Kitchin (public/usenet)" <[email protected]>
01/27/11 12:34 PM >>>
>>I think I see where the problem occurs in the sip trace, but I don't
>>have the sip knowledge to understand why.
>>
>>Any help would be greatly appreciated.
Ok, I've reviewed your traces and your wiresharks. You've got some
serious issues here.
First, It doesn't seem to be the sip trunk provider not liking the
codec. The trunk does successfully go from G.729 to G.711 for the
MoH. And the MoH can be heard in the wireshark RTP.
But here is the big issue. Your phone is sending the reinvite for MoH
or transfer directly to sipxbridge.
Sipxbridge freaks and says "Request not sent by proxy".
I can shed some light on that I think. Verizon required they send us
calls on port 5060. We do nat the port to 5080. We hadn't seen any issue
there, but I guess we have now for some reason.
Verizon --5060-- our router -- 5080 --> sipx
Obviously some of the call setup info is still going to have 5060 in it.
Would that explain why this might be happening?
Your phone should never be sending a reinvite bypassing the proxy. It
should be sending a refer to the proxy and it sends it to sipxbridge
which then reinvites the trunk.
I have seen this in two scenerios
1. You have a second nic in sipx
2. Your DNS is wrong.
I'd start there. Beyond that I'd think you have somthing wrong in your
phone profiles. You could take a phone to factory defaults and
generate a fresh profile that is not part of any phone group that may
have some goofy settings.
-M
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
