I'm struggling with an issue that I was hoping the community could shed some light on. I am in the process of upgrading our RightFax server, and before I migrate the users over, I need to ensure that the routing is working as it should be. The current server which uses H.323 takes a call from our Verizon SIP provider routes it through Session Manager, strips off the first 8 digits, and then adds a 199. I am trying to use 1 of the numbers from that range as a test. I don't necessarily need to strip anything off as the RightFax can handle whatever digits are presented. I just can't seem to get it past an adaptation in our SM. Even if I use a totally random number that is not part of the old RightFax server, it still gets stopped by the adaption that I don't want.
Scenario – Migrating RightFax server from H.323 to SIP
Issue – Test fax DID (212-299-6003) is choosing wrong ingress adaptation and subsequently applying the wrong originating location and any other rules or polices that are in place (see trace below). It may be getting confused from the current set of fax numbers that all start with +1212299, but are routed through Session Manager and subsequently CM.
What should it do? – I've attached a Word document with the 2 traces that I am referring to.
Configurations:
Communication Manager
CM SIP Trunk: 10
CM Routing Pattern: 25
CM Signaling Group: 25 (Near End: CLAN02B04 Far End: HHR_RightFax TCP: 5066 Domain: fax.hugheshubbard.com)
IP Network Region: 8 (IP Codec Set: 1)
Node Name: HHR_RightFax 10.100.10.182
Session Manager
Domains: fax.hugheshubbard.com
Locations: HHR_RightFax
Adaptations: HHR_RightFax
SIP Entities: HHR_RightFax (Other) pdcpasm01 (Session Manager)
Entity Links: HHR_RightFax_TCP and HHR_RightFax_UDP
Routing Policies: HHR_RightFax
Dial Patterns: +12122996003 12 12 SIP Domain: fax.hugheshubbard.com Originating Locations and Routing Policies: HHR_RightFax RightFax Routing HHR_RightFax 0 HHR_RightFax NY Fax Numbers
198 7 7 SIP Domain: fax.hugheshubbard.com Originating Locations and Routing Policies: HHR_RightFax RightFax Routing HHR_RightFax 0 HHR_RightFax NY Fax Numbers
DNS Subzone
fax.hugheshubbard.com
Scenario – Migrating RightFax server from H.323 to SIP
Issue – Test fax DID (212-299-6003) is choosing wrong ingress adaptation and subsequently applying the wrong originating location and any other rules or polices that are in place (see trace below). It may be getting confused from the current set of fax numbers that all start with +1212299, but are routed through Session Manager and subsequently CM.
What should it do? – I've attached a Word document with the 2 traces that I am referring to.
Configurations:
Communication Manager
CM SIP Trunk: 10
CM Routing Pattern: 25
CM Signaling Group: 25 (Near End: CLAN02B04 Far End: HHR_RightFax TCP: 5066 Domain: fax.hugheshubbard.com)
IP Network Region: 8 (IP Codec Set: 1)
Node Name: HHR_RightFax 10.100.10.182
Session Manager
Domains: fax.hugheshubbard.com
Locations: HHR_RightFax
Adaptations: HHR_RightFax
SIP Entities: HHR_RightFax (Other) pdcpasm01 (Session Manager)
Entity Links: HHR_RightFax_TCP and HHR_RightFax_UDP
Routing Policies: HHR_RightFax
Dial Patterns: +12122996003 12 12 SIP Domain: fax.hugheshubbard.com Originating Locations and Routing Policies: HHR_RightFax RightFax Routing HHR_RightFax 0 HHR_RightFax NY Fax Numbers
198 7 7 SIP Domain: fax.hugheshubbard.com Originating Locations and Routing Policies: HHR_RightFax RightFax Routing HHR_RightFax 0 HHR_RightFax NY Fax Numbers
DNS Subzone
fax.hugheshubbard.com
