[VoiceOps] ACME Contact Header rewrite
lriemer at bestline.net
Wed Oct 7 15:17:24 EDT 2009
Yes, reg caching is disabled on that sip-interface. The registration
requests come through with an acceptable Contact header. The header
retains the original host and the ACME only adds its IP in a maddr tag.
However, every other non-registration dialog contains a Contact header
host rewritten with the ACME's IP.
Mark Holloway wrote:
> When registration-caching is enabled the SD automatically rewrites the
> contact header. Do you have it enabled?
> You may want to read the ACLI configuration guide section titled
> SIPconnect > Modifications to Registration Caching Behavior.
> On Oct 7, 2009, at 11:40 AM, anorexicpoodle wrote:
>> Do you have global-contact configured in the sip-config options
>> tokenizing the contact header?
>> If you dont need the contact-header tokenized like this you can
>> remove global-contact from the sip-config but this is a global
>> setting so be very certain.
>> Alternatively if you need that function elsewhere, just write some
>> HMR to re-write the contact into whatever form MS requires,
>> substituting the from/to or whatever you desire, this is exactly what
>> I have done to work around elements that cannot handle the length of
>> the global-contact header.
>> On Wed, 2009-10-07 at 13:09 -0500, Lee Riemer wrote:
>>> Anyone know how to disable the Contact rewrite? I'm trying to build a
>>> PBX in a Metaswitch and the configured SIP binding has an ACME as it's
>>> proxy. I have outbound working fine, but it breaks on inbound as the MS
>>> is looking for the PBX IP in the Contact header, not the ACME's. I
>>> understand the point is for the signaling to come back to the ACME, but
>>> the proxy setting in the SIP binding takes care of that.
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps