Hi all, I am kind of newbie to the voice world and I needed some help setting up my dial-peers:
I have a call manager managing all my voice calls and I have also a SIP faxing software for sending faxes out, what I needed is when I am sending out faxes to match the correct dial-peer, but ny config right now is matching always the dial-peer for the call manager. could you help?
1) Incoming called number will always match before answer address. If you want to match with answer address 'incoming called-number .' can't exist anywhere. You would need to use answer-address to also match CUCM dial peers.
2) Your DTMF for your incoming fax dial peer isn't going to work because SIP endpoints do not use H245.
3) You may be able to get this to work by putting the fax protocol configuration under your CUCM dial peer. Adding fax capabilities won't break anything with CUCM.
4) Take 'fallback cisco' off your fax protocol configuration, as your fax server doesn't support it.
Thanks, it was not me that configured the voice gateway and I am trying to understand it's configuration so I can then make the changes I need.
Frim what I already gathered it seems to me that dial peers 1 and 2 are being used both for inbound and outbound matching. Peer 1, match for destination-pattern 12.. when making inbound calls and incoming called-number . for outbound, the same for dial peer 2 is matching destination-pattern 9T for outbound and incoming called-number . for inbound, am I right?
I think that if I want to remove the "incoming called-number ." statement for the dial peer 1 I would have to configure "answer address" or setup another dial peer for inbound matching for CM is that correct?
You should remove incoming called number . if you would like to use answer address.
That leaves 4 options:
Match on a more specific incoming called number that would not intersect with what the fax server would dial (probably not an option)
Configure answer-address on dial peers for your CUCM DID (ANI from GW perspective) range.
Allow for dial peer hunt algorithm to use the 3rd rule, which is match the incoming dial peer against the CALLING number with a destination pattern. The idea here is that if you are pointing a dial peer to it, and the caller id matches it, you should probably use that dial peer. This is messy because often with translations or caller-id masks the numbers you route to CUCM are not the same as the caller ID you will receive. But it is an option.
The fourth is to use translations so that you can match your dial peers. This would be something like adding ## to the calling number and stripping it off your outgoing dial peer, but use it to match your incoming dial peer. Or, prefix numbers on your faxing dial plan and use that to match with an 'incoming called-number .T' This is a little more of a hack, but it's easier to configure and wrap your head around.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...