Has anyone used an MBG instance as a SIP proxy before? Eg. mid-call features, etc.
In the past I've had it running, and all has been ok, but for some reason it now seems that as soon as you point the 3300 to the MBG instance for it's SIP proxy, calls fail.
A tcpdump on the MBG server shows that the call comes back with a 404 response. The trunk registers ok, and I can't spot any difference between a tcpdump from the 3300 going directly out and the MBG in the middle as the proxy.
The end result is as below when you capture on the MBG:
|Time | 192.168.xx.x |
| | | 192.168.x.x |
|8.167 | INVITE SDP (g729 g711A g711U L16RTPType-121 te...hone-eventRT) |SIP From: "X" <sip:xxxxx@provider To:<sip:yyy@provider
| |(5060) ------------------> (5060) |
|8.168 | 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|8.169 | 404 Not Found |SIP Status
| |(5060) <------------------ (5060) |
|8.185 | ACK | |SIP Request
| |(5060) ------------------> (5060) |
It is quite odd as the trunk registers ok, and everything appears normal, but the 404 is returned upon dialing.
I'm banging my head against the wall, and just thought that others out there might be able to change my direction of troubleshooting, as I've been looking at it too much and now seem to have tunnel vision on the problem!